Structure of MAC sub-header for supporting next generation mobile communication system and method and apparatus using the same

ABSTRACT

A communication technique of fusing a fifth generation (5G) communication system for supporting higher data transmission rate beyond a fourth generation (4G) system with an Internet of things (IoT) technology and a system thereof are provided. The communication technique may be used for an intelligent service (for example, a smart home, a smart building, a smart city, a smart car or a connected car, health care, digital education, a retail business, a security and safety related service, or the like) based on the 5G communication technology and the IoT related technology. A method for defining media access control (MAC) sub-header structures suitable for a next generation mobile communication system and applying the MAC sub-header structures to provide a high data transmission rate and a low latency in the next generation mobile communication system is provided.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of prior application Ser.No. 16/566,152, filed on Sep. 10, 2019, which is based on a continuationof prior application Ser. No. 16/287,584, filed on Feb. 27, 2019, whichhas issued as U.S. Pat. No. 10,410,973 on Sep. 17, 2019; which is acontinuation application of prior application Ser. No. 15/802,051, filedon Nov. 2, 2017, which has issued as U.S. Pat. No. 10,257,747 on Apr. 9,2019; and which was based on and claimed priority under 35 U.S.C. §119(a) of a Korean patent application number 10-2016-0146353, filed onNov. 4, 2016, in the Korean Intellectual Property Office, of a Koreanpatent application number 10-2016-0150848, filed on Nov. 14, 2016, inthe Korean Intellectual Property Office, of a Korean patent applicationnumber 10-2016-0179455, filed on Dec. 26, 2016, in the KoreanIntellectual Property Office, and of a Korean patent application number10-2017-0026682, filed on Feb. 28, 2017, in the Korean IntellectualProperty Office, the disclosure of each of which is incorporated byreference herein in its entirety.

TECHNICAL FIELD

The present disclosure relates to an operation of a terminal and a basestation in a next generation mobile communication system. Morespecifically, the present disclosure relates to a structure of a mediaaccess control (MAC) sub-header for supporting a next generation mobilecommunication system and a method and an apparatus using the same.

BACKGROUND

To meet a demand for radio data traffic that is on an increasing trendsince commercialization of a fourth generation (4G) communicationsystem, efforts to develop an improved fifth generation (5G)communication system or a pre-5G communication system have beenconducted. For this reason, the 5G communication system or the pre-5Gcommunication system is called a beyond 4G network communication systemor a post long term evolution (LTE) system. To achieve a high datatransmission rate, the 5G communication system is considered to beimplemented in a very high frequency millimeter wave (mmWave) band(e.g., like 60 GHz band). To relieve a path loss of a radio wave andincrease a transfer distance of a radio wave in the super high frequencyband, in the 5G communication system, technologies, such as beamforming,massive multi-input multi-output (massive MIMO), full dimensional MIMO(FD-MIMO), an array antenna, analog beamforming, and a large scaleantenna have been discussed. Further, to improve a network of thesystem, in the 5G communication system, technologies, such as an evolvedsmall cell, an advanced small cell, a cloud radio access network (cloudRAN), an ultra-dense network, a device to device communication (D2D), awireless backhaul, a moving network, cooperative communication,coordinated multi-points (CoMP), and reception interference cancellationhave been developed. In addition to this, in the 5G system, hybrid FSKand QAM modulation (FQAM) and sliding window superposition coding (SWSC)that are an advanced coding modulation (ACM) scheme and a filter bankmulti carrier (FBMC), a non-orthogonal multiple access (NOMA), and asparse code multiple access (SCMA) that are an advanced accesstechnology, and so on have been developed.

The Internet is being evolved from a human-centered connection networkthrough which a human being generates and consumes information to theInternet of Things (IoT) network having information between distributedcomponents like things transmitted and received therethrough andprocessing the information. The Internet of Everything (IoE) technologyin which the big data processing technology, and the like, is combinedwith the IoT technology by connection with a cloud server, and the like,has also emerged. To implement the IoT, technology elements, such as asensing technology, wired and wireless communication and networkinfrastructure, a service interface technology, and a securitytechnology, have been required. Recently, technologies, such as a sensornetwork, machine to machine (M2M), and machine type communication (MTC)for connecting between things have been researched. In the Internet ofthings (IoT) environment, an intelligent Internet technology (IT)service that generates anew value in human life by collecting andanalyzing data generated in the connected things may be provided. TheIoT may apply for fields, such as a smart home, a smart building, asmart city, a smart car or a connected car, a smart grid, health care,smart appliances, and an advanced healthcare service, by fusing andcombining the existing information technology (IT) with variousindustries.

Therefore, various tries to apply the 5G communication system to the IoTnetwork have been conducted. For example, the 5G communicationtechnologies, such as the sensor network, the M2M, and the MTC, havebeen implemented by techniques, such as the beamforming, the MIMO, andthe array antenna. The application of the cloud RAN as the big dataprocessing technology described above may also be considered as anexample of the fusing of the 5G communication technology with the IoTtechnology.

The next generation mobile communication systems aim at a higher datarate and a lower latency. Therefore, a need exists for a more efficientdata transport format.

The above information is presented as background information only toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present disclosure.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentdisclosure is to provide structures of a media access control (MAC)sub-header suitable for a next generation mobile communication systemand a method and an apparatus using the same, MAC packet data unit (PDU)structures suitable for a next generation mobile communication systemand a method and an apparatus for selecting the same, and a method andan apparatus for applying padding in the MAC PDU structures suitable fora next generation mobile communication system.

Another aspect of the present disclosure is to provide a method forreducing power consumption of a terminal upon transmitting/receivingdata in an inactive state or receiving a paging signal in a nextgeneration mobile communication system.

Another aspect of the present disclosure is to provide a next generationmobile communication system which provides a flow-based quality ofservice (QoS) but does not have an interface (Uu interface) forsupporting the flow-based QoS, unlike the long-term evolution (LTE) ofthe related art.

Another aspect of the present disclosure is to provide a method and anapparatus for performing a dual-registered operation in a nextgeneration mobile communication system. Another aspect of the presentdisclosure is to provide a method for operating an new radio (NR) radiolink control (RLC) apparatus and an NR packet data convergence protocol(PDCP) apparatus in a next generation mobile communication system sincean efficient data transport format is required to provide a servicehaving a high data rate and a low latency in the next generation mobilecommunication system.

Another aspect of the present disclosure is to provide a method and anapparatus for proposing and selecting MAC PDU structures suitable for anext generation mobile communication system.

Another aspect of the present disclosure is to provide a definition of acondition and a procedure of selecting resource pools if terminalssupporting communication between a vehicle and a pedestrian terminalreceive a resource pool for a random resource selection and a resourcepool for a partial sensing operation from a base station.

In accordance with an aspect of the present disclosure, it is possibleto increase the data processing efficiency by defining the structures ofthe MAC sub-header suitable for the next generation mobile communicationsystem and proposing the method and apparatus using the same.

In accordance with another aspect of the present disclosure, it ispossible to provide the service having the high data rate and the lowlatency by proposing the MAC PDU structures suitable for the nextgeneration mobile communication system and proposing the method andapparatus for selecting the same.

In accordance with another aspect of the present disclosure, it ispossible to increase the data processing efficiency by proposing themethod and apparatus for applying the padding in the MAC PDU structuressuitable for the next generation mobile communication system.

In accordance with another aspect of the present disclosure, it ispossible to reduce the power consumption of the terminal in the inactivestate and make the data transmission/reception and the reception of thepaging signal efficient by proposing the method for setting adiscontinuous reception period of an inactive state in a next generationmobile communication system.

In accordance with another aspect of the present disclosure, it ispossible to support the flow-based QoS in the Uu interface by allowingthe radio interface to support the flow-based QoS and including theconditional or simplified QoS flow identifier (ID) in the nextgeneration mobile communication system.

In accordance with another aspect of the present disclosure, it ispossible to apply the method and an apparatus for performing adual-registered operation in a next generation mobile communicationsystem to the inter-system handover or the inter-heterogeneous systemcarrier aggregation technology or the like.

In accordance with another aspect of the present disclosure, it ispossible to correctly set the operations of the NR RLC apparatus and theNR PDCP apparatus in the next generation mobile communication system tolink the apparatuses with the RLC apparatus and the PDCP apparatus ofthe LTE system without any problem, thereby providing services.

In accordance with another aspect of the present disclosure, it ispossible to provide the service having the high data rate and the lowlatency by proposing the MAC PDU structures suitable for the nextgeneration mobile communication system and proposing the method andapparatus for selecting the same.

In accordance with another aspect of the present disclosure, it ispossible to efficiently manage the power consumption of the pedestrianterminal and increase the transmission success rate of the packet havingthe high priority, by proposing the conditions and procedures forselecting the resource pools of the terminals supporting thecommunication between the vehicle and the pedestrian terminal.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present disclosure will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1A is a diagram illustrating a structure of a long term evolution(LTE) system according to an embodiment of the present disclosure;

FIG. 1B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure;

FIG. 1C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure;

FIG. 1D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure;

FIGS. 1EA, 1EB, and 1EC are diagrams illustrating a first media accesscontrol (MAC) packet data unit (PDU) structure for a next generationmobile communication system according to an embodiment of the presentdisclosure;

FIG. 1F is a diagram illustrating a first MAC sub-header structuresuitable for the first MAC PDU structures for a next generation mobilecommunication system according to an embodiment of the presentdisclosure;

FIG. 1G is a diagram illustrating a second MAC sub-header structuresuitable for the first MAC PDU structures for a next generation mobilecommunication system according to an embodiment of the presentdisclosure;

FIG. 1H is a diagram illustrating a third MAC sub-header structuresuitable for the first MAC PDU structures for a next generation mobilecommunication system according to an embodiment of the presentdisclosure;

FIG. 1I is a diagram illustrating an operation of a terminal related toa method for applying an MAC sub-header according to an embodiment ofthe present disclosure;

FIG. 1J is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure;

FIG. 1K is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure;

FIG. 1L is a diagram illustrating detailed devices of a terminalaccording to an embodiment of the present disclosure;

FIGS. 1MA and 1MB are diagrams illustrating in a time sequence a processof constructing MAC sub-headers and MAC subscriber data units (SDUs) inadvance before a terminal is allocated a transmission resource,constructing an MAC PDU by generating an MAC control element (CE)simultaneously with constructing an MAC PDU consisting of the MACsub-headers and MAC SDUs generated in advance if an uplink transmissionresource is allocated, and locating the MAC CE at a tail of the MAC PDUaccording to embodiments of the present disclosure;

FIGS. 1NA and 1NB are diagrams illustrating in a time sequence a processof constructing MAC sub-headers and MAC SDUs in advance before aterminal is allocated a transmission resource, constructing an MAC PDUby generating an MAC CE simultaneously with constructing an MAC PDUconsisting of the MAC sub-headers and MAC SDUs generated in advance ifan uplink transmission resource is allocated, and locating the MAC CE ata head of the MAC PDU according to embodiments of the presentdisclosure;

FIGS. 10A and 10B are diagrams illustrating in a time sequence a processof constructing MAC sub-headers and MAC SDUs in advance before aterminal is allocated a transmission resource, constructing an MAC PDUby generating an MAC CE simultaneously with constructing an MAC PDUconsisting of the MAC sub-headers and MAC SDUs generated in advance ifan uplink transmission resource is allocated, and locating the MAC CE ata head of the MAC PDU according to embodiments of the presentdisclosure;

FIG. 2A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure;

FIG. 2B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure;

FIG. 2C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure;

FIG. 2D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure;

FIGS. 2EA and 2EB are diagrams illustrating a first MAC PDU structurefor a next generation mobile communication system according toembodiments of the present disclosure;

FIGS. 2FA, 2FBA, 2FBB, 2FCA, 2FCB, 2FDA, 2FDB, 2FEA, 2FEB, and 2FF arediagrams illustrating a second MAC PDU structure for a next generationmobile communication system according to embodiments of the presentdisclosure;

FIGS. 2GA, 2GB, and 2GC are diagrams illustrating a third MAC PDUstructure for a next generation mobile communication system according toembodiments of the present disclosure;

FIG. 2H is a diagram illustrating MAC SDU (or RLC PDU) structures for anext generation mobile communication system according to an embodimentof the present disclosure;

FIG. 2I is a block diagram illustrating an internal structure of aterminal according to an embodiment the present disclosure;

FIG. 2J is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure;

FIG. 3A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure;

FIG. 3B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure;

FIG. 3C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure;

FIG. 3D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure;

FIGS. 3EA and 3EB are diagrams illustrating a first MAC PDU structurefor a next generation mobile communication system according toembodiments of the present disclosure;

FIGS. 3FA, 3FBA, 3FBB, 3FCA, 3FCB, 3FDA, 3FDB, 3FEA, and 3FEB arediagrams illustrating a second MAC PDU structure for a next generationmobile communication system according to embodiments of the presentdisclosure;

FIGS. 3GA, 3GB, and 3GC are diagrams illustrating a third MAC PDUstructure for a next generation mobile communication system according toembodiments of the present disclosure;

FIGS. 3HA and 3HB illustrate a first method for applying paddingaccording to an embodiment of the present disclosure;

FIGS. 3IA and 3IB illustrate a second method for applying paddingaccording to an embodiment of the present disclosure;

FIG. 3J is a diagram illustrating a third method for applying paddingaccording to an embodiment of the present disclosure;

FIG. 3K is a diagram illustrating a fourth method for applying paddingof according to an embodiment the present disclosure;

FIG. 3L is a diagram illustrating an operation of a terminal related tofirst, second, and fifth methods for applying padding according to anembodiment of the present disclosure;

FIG. 3M is a diagram illustrating an operation of a terminal related tothird, fourth, sixth, and seventh methods for applying padding accordingto an embodiment of the present disclosure;

FIG. 3N is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure;

FIG. 3O is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure;

FIG. 4A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure;

FIG. 4B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure;

FIG. 4C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure;

FIG. 4D is a diagram illustrating a DRX operation for an IDLE terminalin an LTE system according to an embodiment of the present disclosure;

FIG. 4E is a diagram illustrating a DRX operation for a terminal in anRR connection state in an LTE system according to an embodiment of thepresent disclosure;

FIG. 4F is a diagram illustrating a DRX operation in an INACTIVE stateaccording to an embodiment of the present disclosure;

FIG. 4G is a diagram illustrating an operation of a terminal forperforming a DRX in an INACTIVE state according to an embodiment of thepresent disclosure;

FIG. 4H is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure;

FIG. 4I is a block diagram illustrating a configuration of an NR basestation according to an embodiment of the present disclosure;

FIG. 5A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure;

FIG. 5B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure;

FIG. 5C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure;

FIG. 5D is a diagram illustrating new functions handling quality ofservice (QoS) in an NR system according to an embodiment of the presentdisclosure;

FIG. 5E is a diagram illustrating a first structure of an access stratumMultiplexing Layer (ASML) protocol according to an embodiment of thepresent disclosure;

FIG. 5F is a diagram illustrating an ASML header in a first structure ofan ASML according to an embodiment of the present disclosure;

FIG. 5G is a diagram illustrating an operation of a terminal of a firststructure of an ASML according to an embodiment of the presentdisclosure;

FIG. 5H is a second structure of an ASML protocol according to anembodiment of the present disclosure;

FIG. 5I is a diagram illustrating a packet data convergence protocol(PDCP) header in a second structure of an ASML according to anembodiment of the present disclosure;

FIG. 5J is a diagram illustrating an operation of a terminal of a secondstructure of an ASML according to an embodiment of the presentdisclosure;

FIG. 5K is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure;

FIG. 5L is a block diagram illustrating a configuration of an NR basestation according to an embodiment of the present disclosure;

FIG. 6A is a diagram illustrating an inter-system handover by applyingdual-registered in a next generation mobile communication systemaccording to an embodiment of the present disclosure;

FIG. 6B is a diagram illustrating a signaling flow chart when a terminalmoves to a service area of an LTE system of a next generation mobilecommunication system according to an embodiment of the presentdisclosure;

FIG. 6C is a diagram illustrating a signaling flow chart when a terminalmoves to a service area of an LTE system of a next generation mobilecommunication system according to an embodiment of the presentdisclosure;

FIG. 6D is a diagram illustrating a process of determininginitialization of a dual-registered operation according to an embodimentof the present disclosure;

FIG. 6E is a diagram illustrating a process of providing, by a terminal,information necessary for a source system according to an embodiment ofthe present disclosure;

FIG. 6F is a diagram illustrating a process of confirming access barringbefore a terminal performs an attach operation to a target cellaccording to an embodiment of the present disclosure;

FIG. 6G is a diagram illustrating a method for performing, by aterminal, an uplink power control according to an embodiment of thepresent disclosure;

FIG. 6H is a diagram illustrating an operation flow block forperforming, by a terminal, an uplink power control according to anembodiment of the present disclosure;

FIG. 6I is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure;

FIG. 6J is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure;

FIG. 7A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure;

FIG. 7B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure;

FIG. 7C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure;

FIG. 7D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure;

FIG. 7E is a diagram illustrating a procedure of setting, by a terminal,apparatuses of each layer in a next generation mobile communicationsystem according to an embodiment of the present disclosure;

FIG. 7F is a diagram illustrating scenarios which allow a terminal toreceive services through an LTE base station and an NR base station in anext generation mobile communication system according to an embodimentof the present disclosure;

FIG. 7G is a diagram illustrating a scenario which allows a terminal toreceive services through an LTE base station and an NR base station in anext generation mobile communication system according to an embodimentof the present disclosure;

FIG. 7H is a diagram illustrating an operation of a terminal accordingto 7-1-th, 7-2-th, 7-3-th, and 7-7-th embodiments of the presentdisclosure;

FIG. 7I is a diagram illustrating an operation of a base stationaccording to 7-4-th, 7-5-th, 7-6-th, and 7-8-th embodiments of thepresent disclosure;

FIG. 7J is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure;

FIG. 7K is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure;

FIG. 8A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure;

FIG. 8B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure;

FIG. 8C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure;

FIG. 8D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure;

FIG. 8E is a diagram illustrating a first MAC PDU structure for a nextgeneration mobile communication system according to an embodiment of thepresent disclosure;

FIGS. 8FA, 8FB, 8FC, 8FD, 8FE, 8FF, 8FG, 8FH, and 8FI are diagrams of asecond MAC PDU structure for a next generation mobile communicationsystem according to embodiments of the present disclosure;

FIG. 8G is a diagram illustrating a third MAC PDU structure for a nextgeneration mobile communication system according to an embodiment of thepresent disclosure;

FIG. 8H is a diagram illustrating an operation of a terminal in a nextgeneration mobile communication system according to 8-1-th and 8-2-thembodiments of the present disclosure;

FIG. 8I is a diagram illustrating an operation of a terminal in a nextgeneration mobile communication system according to 8-3-th and 8-4-thembodiments of the present disclosure;

FIG. 8J is a diagram illustrating an operation of a terminal in a nextgeneration mobile communication system according to a 8-5-th embodimentof the present disclosure;

FIG. 8K is a diagram illustrating a process of performing, by an RLClayer, segmentation or concatenation according to a 8-6-th embodiment ofthe present disclosure;

FIG. 8L is a diagram illustrating an RLC header structure according to a8-6-th embodiment of the present disclosure;

FIG. 8M is a diagram illustrating a segment offset (SO)-basedsegmentation procedure according to a 8-7-th embodiment of the presentdisclosure;

FIG. 8N is a diagram illustrating an RLC header structure according to a8-7-th embodiment of the present disclosure;

FIG. 8O is a diagram illustrating a segmentation control information(SCI)-based segmentation procedure according to a 8-8-th embodiment ofthe present disclosure;

FIG. 8P is a diagram illustrating an RLC header structure according toan 8-8-th embodiment of the present disclosure;

FIG. 8Q is a diagram illustrating a segmentation information (SI),framing information (FI), last segment field (LSF)-based segmentationprocedure according to a 8-9-th embodiment of the present disclosure;

FIG. 8R is a diagram illustrating an RLC header structure according to a8-9-th embodiment of the present disclosure;

FIG. 8S is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure;

FIG. 8T is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure;

FIG. 9A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure;

FIG. 9B is a diagram illustrating a vehicle-to-pedestrian (V2P)communication according to an embodiment of the present disclosure;

FIG. 9C is a diagram illustrating a procedure of a random resourceselection of a V2P terminal operated in mode 3 according to anembodiment of the present disclosure;

FIG. 9D is a diagram illustrating a procedure of a random resourceselection of a V2P terminal operated in mode 4 according to anembodiment of the present disclosure;

FIG. 9E is a diagram illustrating a partial sensing operation in V2Paccording to an embodiment of the present disclosure;

FIG. 9F is a diagram illustrating a method for determining a resourcepool of a V2P terminal operated in mode 3 according to a 9-1-thembodiment of the present disclosure;

FIG. 9G is a diagram illustrating a method for determining a resourcepool of a V2P terminal operated in a terminal-autonomous mode accordingto a 9-1-th embodiment of the present disclosure.

FIG. 9H is a diagram illustrating a method for determining a resourcepool of a V2P terminal operated in a base station control mode accordingto a 9-2-th embodiment of the present disclosure;

FIG. 9I is a diagram illustrating a method for determining a resourcepool of a V2P terminal operated in a terminal autonomous mode accordingto a 9-2-th embodiment of the present disclosure;

FIG. 9J is a diagram illustrating an operation of a terminal accordingto a 9-1-th embodiment of the present disclosure;

FIG. 9K is a diagram illustrating an operation of a terminal accordingto a 9-2-th embodiment of the present disclosure;

FIG. 9L is a block configuration diagram illustrating a terminalaccording to an embodiment of the present disclosure; and

FIG. 9M is a block configuration diagram of a base station according toan embodiment of the present disclosure;

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features, andstructures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thepresent disclosure. In addition, descriptions of well-known functionsand constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

By the term “substantially” it is meant that the recited characteristic,parameter, or value need not be achieved exactly, but that deviations orvariations, including for example, tolerances, measurement error,measurement accuracy limitations and other factors known to those ofskill in the art, may occur in amounts that do not preclude the effectthe characteristic was intended to provide.

Further, in an orthogonal frequency division multiplexing (OFDM)-basedwireless communication system, in particular, a 3^(rd) generationpartnership project (3GPP) evolved universal terrestrial radio access(EUTRA) standard will be mainly described. However, a main subject ofthe present disclosure may be slightly changed to be applied to othercommunication systems having similar technical backgrounds and channelforms without greatly departing the scope of the present disclosure,which may be determined by those skilled in the art to which the presentdisclosure pertains. For example, a main subject may also be applied toa multicarrier HSPA supplying the carrier aggregation.

In describing the various embodiments of the present disclosure, adescription of technical contents which are well known to the art towhich the present disclosure belongs and are not directly connected withthe present disclosure will be omitted. The reason why an unnecessarydescription is omitted is to make the gist of the present disclosureclear.

For the same reason, some components are exaggerated, omitted, orschematically illustrated in the accompanying drawings. Further, thesize of each component does not exactly reflect its real size. In eachdrawing, the same or corresponding components are denoted by the samereference numerals.

Various advantages and features of the present disclosure and methodsaccomplishing the same will become apparent from the following detaileddescription of embodiments with reference to the accompanying drawings.However, the present disclosure is not limited to the embodimentsdisclosed herein but will be implemented in various forms. Theembodiments have made disclosure of the present disclosure complete andare provided so that those skilled in the art may easily understand thescope of the present disclosure. Therefore, the present disclosure willbe defined by the scope of the appended claims. Like reference numeralsthroughout the description denote like elements.

In this case, it may be understood that each block of processing flowcharts and combinations of the flow charts may be performed by computerprogram instructions. Since these computer program instructions may bemounted in processors for a general computer, a special computer, orother programmable data processing apparatuses, these instructionsexecuted by the processors for the computer or the other programmabledata processing apparatuses generate means performing functionsdescribed in block(s) of the flow charts. Since these computer programinstructions may also be stored in a computer usable or computerreadable memory of a computer or other programmable data processingapparatuses in order to implement the functions in a specific scheme,the computer program instructions stored in the computer usable orcomputer readable memory may also produce manufacturing articlesincluding instruction means performing the functions described in eachblock of the flow chart. Since the computer program instructions mayalso be mounted on the computer or the other programmable dataprocessing apparatuses, the instructions performing a series ofoperations on the computer or the other programmable data processingapparatuses to generate processes executed by the computer to therebyexecute the computer or the other programmable data processingapparatuses may also provide operations for performing the functionsdescribed in block(s) of the flow charts.

In addition, each block may indicate some of modules, segments, or codesincluding one or more executable instructions for executing a specificlogical function(s). Further, it is to be noted that functions mentionedin the blocks occur regardless of a sequence in some alternativeembodiments of the present disclosure. For example, two blocks that areconsecutively illustrated may be simultaneously performed in fact or beperformed in a reverse sequence depending on corresponding functionssometimes.

Here, the term ‘˜unit’ used in the present embodiment means software orhardware components, such as a field programmable gate array (FPGA) andapplication specific integrated circuits (ASIC) and the ‘˜unit’ performsany roles. However, the meaning of the ‘˜unit’ is not limited tosoftware or hardware. The ‘˜unit’ may be configured to be in a storagemedium that may be addressed and may also be configured to reproduce oneor more processor. Accordingly, for example, the ‘˜unit’ includescomponents, such as software components, object oriented softwarecomponents, class components, and task components and processors,functions, attributes, procedures, subroutines, segments of programcode, drivers, firmware, microcode, circuit, data, database, datastructures, tables, arrays, and variables. The functions provided in thecomponents and the ‘˜units’ may be combined with a smaller number ofcomponents and the ‘˜units’ or may further be separated into additionalcomponents and ‘˜units’. In addition, the components and the ‘˜units’may also be implemented to reproduce one or more central processingunits (CPUs) within a device or a security multimedia card.

First Embodiment

FIG. 1A is a diagram illustrating a structure of a long term evolution(LTE) system according to an embodiment of the present disclosure.

Referring to FIG. 1A, a radio access network of an LTE system isconfigured to include next generation base stations (evolved node B,hereinafter, eNB, Node B, or base station) 1 a-05, 1 a-10, 1 a-15, and 1a-20, a mobility management entity (MME) 1 a-25, and a serving-gateway(S-GW) 1 a-30. User equipment (hereinafter, UE or terminal) 1 a-35accesses an external network through the eNBs 1 a-05 to 1 a-20 and theS-GW 1 a-30.

A user equipment (hereinafter, UE or terminal) 1 a-35 accesses anexternal network through the eNBs 1 a-05 to 1 a-20 and the S-GW 1 a-30.The eNB is connected to the UE 1 a-35 through a radio channel andperforms more complicated role than the existing node B. In the LTEsystem, in addition to a real-time service like a voice over Internetprotocol (VoIP) through the Internet protocol, all the user traffics areserved through a shared channel and therefore an apparatus forcollecting and scheduling status information, such as a buffer status,an available transmit power status, and a channel state of the terminalsis required. Here, the eNBs 1 a-05 to 1 a-20 take charge of thecollecting and scheduling. One eNB generally controls a plurality ofcells. For example, to implement a transmission rate of 100 Mbps, theLTE system uses, as a radio access technology, OFDM in, for example, abandwidth of 20 MHz. Further, an adaptive modulation & coding(hereinafter, called AMC) determining a modulation scheme and a channelcoding rate depending on a channel status of the terminal is applied.The S-GW 1 a-30 is an apparatus for providing a data bearer andgenerates or removes the data bearer according to the control of the MME1 a-25. The MME is an apparatus for performing a mobility managementfunction for the terminal and various control functions and is connectedto a plurality of base stations.

FIG. 1B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure.

Referring to FIG. 1B, the radio protocol of the LTE system is configuredto include packet data convergence protocols (PDCPs) 1 b-05 and 1 b-40,radio link controls (RLCs) 1 b-10 and 1 b-35, and medium access controls(MMCs) 1 b-15 and 1 b-30 in the terminal and the eNB, respectively. ThePDCPs 1 b-05 and 1 b-40 are in charge of operations, such as IP headercompression/decompression. The main functions of the PDCP are summarizedas follows.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer powerdistribution units (PDU)s at PDCP re-establishment procedure for RLC AM)

Reordering function (For split bearers in DC (only support for RLC AM):PDCP PDU routing for transmission and PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layersubscriber data units (SDUs) at PDCP re-establishment procedure for RLCAM)

Retransmission function (Retransmission of PDCP SDUs at handover and,for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure,for RLC AM)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink)

The RLCs 1 b-10 and 1 b-35 reconfigures the PDCP PDU to an appropriatesize to perform the ARQ operation or the like. The main functions of theRLC are summarized as follows.

Data transfer function (Transfer of upper layer PDUs)

ARQ function (Error Correction through ARQ (only for AM data transfer))

Concatenation, segmentation, reassembly functions (Concatenation,segmentation and reassembly of RLC SDUs (only for UM and AM datatransfer))

Re-segmentation function (Re-segmentation of RLC data PDUs (only for AMdata transfer))

Reordering function (Reordering of RLC data PDUs (only for UM and AMdata transfer)

Duplicate detection function (Duplicate detection (only for UM and AMdata transfer))

Error detection function (Protocol error detection (only for AM datatransfer))

RLC SDU discard function (RLC SDU discard (only for UM and AM datatransfer))

RLC re-establishment function (RLC re-establishment)

The media access controls (MACs) 1 b-15 and 1 b-30 are connected toseveral RLC layer apparatus configured in one terminal and perform anoperation of multiplexing RLC PDUs into an MAC PDU and demultiplexingthe RLC PDUs from the MAC PDU. The main functions of the MAC aresummarized as follows.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MACSDUs belonging to one or different logical channels into/from transportblocks (TB) delivered to/from the physical layer on transport channels)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between Logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

Physical layers 1 b-20 and 1 b-25 perform an operation of channel-codingand modulating upper layer data, making the upper layer data as an OFDMsymbol and transmitting the symbol to a radio channel, or demodulatingand channel-decoding the OFDM symbol received through the radio channeland transmitting the demodulated and channel-decoded OFDM symbol to theupper layer.

FIG. 1C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure.

Referring to FIG. 1C, a radio access network of a next generation mobilecommunication system (hereinafter referred to as NR or 5G) is configuredto include a next generation base station (New radio node B, hereinafterNR gNB or NR base station) 1 c-10 and a new radio core network (NR CN) 1c-05. The user terminal (new radio user equipment, hereinafter, NR UE orUE) 1 c-15 accesses the external network through the NR gNB 1 c-10 andthe NR CN 1 c-05.

In FIG. 1C, the NR gNB 1 c-10 corresponds to an evolved node B (eNB) ofthe existing LTE system. The NR gNB is connected to the NR UE 1 c-15 viaa radio channel and may provide a service superior to the existing nodeB. In the next generation mobile communication system, since all usertraffics are served through a shared channel, an apparatus forcollecting state information, such as a buffer state, an availabletransmit power state, and a channel state of the UEs to performscheduling is required. The NR NB 1 c-10 may serve as the device. One NRgNB generally controls a plurality of cells. In order to realizehigh-speed data transmission compared with the current LTE, the NR gNBmay have an existing maximum bandwidth or more, and may be additionallyincorporated into a beam-forming technology may be applied by using OFDMas a radio access technology 1 c-20. Further, an adaptive modulation &coding (hereinafter, called AMC) determining a modulation scheme and achannel coding rate depending on the channel status of the terminal isapplied. The NR CN 1 c-05 may perform functions, such as mobilitysupport, bearer setup, QoS setup, and the like. The NR CN is a devicefor performing a mobility management function for the terminal andvarious control functions and is connected to a plurality of basestations. In addition, the next generation mobile communication systemcan interwork with the existing LTE system, and the NR CN is connectedto the MME 1 c-25 through the network interface. The MME 1 is connectedto the eNB 1 c-30 which is the existing base station.

FIG. 1D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 1D, the radio protocol of the next generation mobilecommunication system is configured to include NR PDCPs 1 d-05 and 1d-40, NR RLCs 1 d-10 and 1 d-35, and NR MACs 1 d-15 and 1 d-30 in theterminal and the NR base station. The main functions of the NR PDCPs 1d-05 and 1 d-40 may include some of the following functions.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Reordering function (PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs)

Retransmission function (Retransmission of PDCP SDUs)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink.)

In this case, the reordering function of the NR PDCP apparatus refers toa function of rearranging PDCP PDUs received in a lower layer in orderbased on a PDCP sequence number (SN) and may include a function oftransferring data to an upper layer in the rearranged order, a functionof recording PDCP PDUs lost by the reordering, a function of reporting astate of the lost PDCP PDUs to a transmitting side, and a function ofrequesting a retransmission of the lost PDCP PDUs.

The main functions of the NR RLCs 1 d-10 and 1 d-35 may include some ofthe following functions.

Data transfer function (Transfer of upper layer PDUs)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Out-of-sequence delivery function (Out-of-sequence delivery of upperlayer PDUs)

ARQ function (Error correction through HARQ)

Concatenation, segmentation, reassembly function (Concatenation,segmentation and reassembly of RLC SDUs)

Re-segmentation function (Re-segmentation of RLC data PDUs)

Reordering function (Reordering of RLC data PDUs)

Duplicate detection function (Duplicate detection)

Error detection function (Protocol error detection)

RLC SDU discard function (RLC SDU discard)

RLC re-establishment function (RLC re-establishment)

In this case, the in-sequence delivery function of the NR RLC apparatusrefers to a function of delivering RLC SDUs received from a lower layerto an upper layer in order, and may include a function of reassemblingand transferring an original one RLC SDU which is divided into aplurality of RLC SDUs and received, a function of rearranging thereceived RLC PDUs based on the RLC sequence number (SN) or the PDCPsequence number (SN), a function of recording the RLC PDUs lost by thereordering, a function of reporting a state of the lost RLC PDUs to thetransmitting side, a function of requesting a retransmission of the lostRLC PDUs, a function of transferring only the SLC SDUs before the lostRLC SDU to the upper layer in order when there is the lost RLC SDU, afunction of transferring all the received RLC SDUs to the upper layerbefore a predetermined timer starts if the timer expires even if thereis the lost RLC SDU, or a function of transferring all the RLC SDUsreceived until now to the upper layer in order if the predeterminedtimer expires even if there is the lost RLC SDU. In this case, theout-of-sequence delivery function of the NR RLC apparatus refers to afunction of directly delivering the RLC SDUs received from the lowerlayer to the upper layer regardless of order, and may include a functionof reassembling and transferring an original one RLC SDU which isdivided into several RLC SDUs and received, and a function of storingthe RLC SN or the PDCP SP of the received RLC PDUs and arranging it inorder to record the lost RLC PDUs.

The NR MACs 1 d-15 and 1 d-30 may be connected to several NR RLC layerapparatus configured in one terminal, and the main functions of the NRMAC may include some of the following functions.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing and demultiplexing function (Multiplexing/demultiplexing ofMAC SDUs)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

The NR PHY layers 1 d-20 and 1 d-25 may perform an operation ofchannel-coding and modulating upper layer data, making the upper layerdata as an OFDM symbol and transmitting them to a radio channel, ordemodulating and channel-decoding the OFDM symbol received through theradio channel and transmitting the demodulated and channel-decoded OFDMsymbol to the upper layer.

The following Table 1 describes the information that may be included inthe MAC header.

TABLE 1 Variables in MAC Header Variable Usage LCID The LCID mayindicate the identifier of the RLC entity that generates the RLC PDU (orMAC SDU) received from the upper layer. Alternatively, the LCID mayindicate the MAC control element (CE) or the padding. Further, the LCIDmay be defined differently depending on the channel to be transmitted.For example, the LCID may be defined differently according to DL-SCH,UL- SCH, and MCH. L The L may indicate a length of the MAC SDU, and mayindicate a length of the MAC CE having a variable length. In the case ofthe MAC CE having a fixed length, the L-field may be omitted. TheL-field may be omitted for predetermined reasons. The predeterminedreasons are the case where the size of the MAC SDU is fixed, the size ofthe MAC PDU is informed from the transmitting side to the receivingside, or the length may be calculated by calculation at the receivingside. F The F indicates the size of the L-field. If there is no L-field,the F may be omitted, and if there is the F-field, the size of theL-field can be limited to a predetermined size. F2 The F2 indicates thesize of the L-field. If there is no L-field, the F2 may be omitted, andif there is the F2-field, the size of the L-field may be limited to apredetermined size and the L-field may be limited to a size differentfrom the F-field. For example, the F2-field may indicate a larger sizethan the F-field. E E indicates other headers in the MAC heater. Forexample, if the E has a value of 1, variables of another MAC header maybe come. However, if the E has a value of 0, the MAC SDU, the MAC CE, orthe Padding may be come. R Reserved bit.

FIGS. 1EA to 1EC are diagrams illustrating a first MAC PDU structure fora next generation mobile communication system according to an embodimentof the present disclosure.

Meanwhile, the embodiment of the configuration and transmission of theMAC PDU of the terminal or the base station described below may beinterpreted as an operation between the transmitting end and thereceiving end. In other words, the process of transmitting the uplinkMAC PDU configured by the terminal which is the transmitting end to thebase station which is the receiving end may be applied to the process oftransmitting the downlink MAC PDU configured by the base station whichis the transmitting end to the terminal which is the receiving end.

Referring to FIGS. 1EA to 1EC, a repeating structure is illustrated inwhich the MAC sub-header and the MAC SDU are arranged and isadvantageous to allow a terminal to previously configure and preparedata before being allocated an uplink transmission resource (UL grant).For example, the terminal may receive several RLC PDUs from the RLClayer before being allocated the uplink transmission resource, and theMAC layer may immediately generate the MAC SDU together with the MACsub-header from the received RLC PDU. Therefore, the first MAC PDUstructure is advantageous to sequentially manage the MAC sub-header andthe MAC SDUs generated in advance, and is advantageous since after theuplink transmission resource is received, the MAC PDUs are sequentiallyconfigured with the MAC sub-header and the MAC SDUs generated inadvance. In addition, the structure is a repeating structure in whichthe MAC sub-header and the MAC SDU are arranged, and is a structuresuitable to reduce a terminal processing time using a hardwareaccelerator at transmitting/receiving ends in a hardware manner sincethe MAC sub-header is a header having a fixed size and in most cases,the size of the RLC header and the PDCP header may also have a fixedsize. In addition, the transmitting end may transmit the MAC sub-headerand the MAC SDU to the PHY layer in units of the MAC sub-header and theMAC SDU processed from the head in the MAC layer to accelerate aprocessing rate, and the receiving end may transmit the MAC sub-headerand the MAC SDU to the RLC layer in units of the MAC sub-header and theMAC SDU processed from the head in the MAC layer to accelerate theprocessing rate.

Referring to FIGS. 1EA to 1EC, 1E-(Format 3-1) may store one MAC SDU orMAC CE. In the above structure, the MAC header is located at a frontpart and the payload is located at a rear part. The header may includethe variables described in Table 1 except for the L-field, andinformation other than the variables described in Table 1. In the1e-(Format 3-1), since only one MAC CE or MAC SDU is included, theL-field may be omitted. Because the size of the MAC sub-header is knownas well as the size of the MAC PDU is known at the reception side byindicating a size of a transport block (TB) by an L1 control signal,that is, PDCCH, the size of the MAC SDU may be known immediately.Therefore, it is not necessary to separately indicate the size of theMAC SDU by the L field.

1e-(Format 3-2a) has a structure, such as a sub-header, a MAC CE, asub-header, a MAC SDU, a sub-header, and a padding and the first MAC PDUstructure has a repeating structure, such as a sub-header, a payload, asub-header, and a payload. The 1e-(Format 3-2a) structure is largelydivided into a MAC CE part and a MAC SDU part. The MAC CEs may belocated at a front part in the order in which they are first generated.In the MAC SDU part, a last segment of one MAC SDU (or RLC PDU or RLCSDU) may be located at a head thereof and a first segment of one MAC SDU(or RLC PDU or RLC SDU) may be located at a tail thereof. In this case,the MAC CE may be a MAC CE associated with scheduling information, suchas a buffer status report (BSR) and a power headroom report (PHR), andlocating the generated MAC CEs at the head thereof as in the 1e-(Format3-2a) may be very advantageous in the scheduling of the base station.For example, if the base station receives the MAC PDU from the terminaland first reads the MAC CEs associated with the scheduling information,the scheduling information may be directly provided to a base stationscheduler to quickly schedule several terminals.

In addition, in this case, the MAC CEs may indicate various information.For example, there may be a kind of MAC CEs, such as a MAC CE indicatinginformation for several antenna configurations (FD-MIMO), a MAC CE (MACCE indicating how often or how many times the channel measurement isperformed or at which time/frequency transmission resource themeasurement and reporting are performed for the purpose of channel stateinformation-reference signal (CSI-RS), a sounding reference signal(SRS), a demodulated reference signal (DMRS), or the like) for channelmeasurement, a MAC CE (MAC CE used for the purpose of indicatingmobility of the terminal with L2 mobility, i.e., the MAC CE andindicating an inter-cell handover related instruction of the terminal)for quickly supporting the mobility of the terminal, a MAC CE (MAC CEindicating by which beam a service is received, the measurement isperformed, and information on the number of beams, time/frequencyresources of the beam, or the like) indicating beam-related informationrequired when the terminal performs camp on, random access, or cellmeasurement, a MAC CE (MAC CE (MAC CE indicating whether to use ShortTTI, whether to use general TTI (1 ms), or whether to use longer TTI, orthe like) dynamically indicating TTI to be used by the terminal, a MACCE (MAC CE indicating a dedicated transmission resource requesting SR tothe terminal) indicating information on the scheduling request (SR), anda MAC CE indicating transmission resource information/configurationinformation or the like required for the terminal supporting an URLLCservice.

The sub-header may include some of the variables described in Table 1,and information other than the variables described in Table 1. Thepadding is stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 1e-(Format3-2a). For example, the header of the front part becomes the informationindicating the payload of the rear part. The 1e-(Format 3-2a) structureis characterized in that an L-field is not included in the lastsub-header. Since the size of the transport block (TB) is indicated bythe L1 control signal, that is, the PDCCH, the size of the MAC PDU maybe already known at the receiving side, and L-field values of the restsub-headers may be confirmed at the receiving side and subtracted fromthe entire length of the MAC PDU to estimate the length of the last MACSDU. In this case, if segmentation is generated when the MAC PDU istransmitted in the previous uplink transmission resource and thus apredetermined segment remains, the remaining segments may be processedby being put in the front part of the MAC SDU part. Therefore, thereceiving side may first receive and re-assemble the data of the RLC PDUwith the lowest RLC sequence number.

The 1e-(Format 3-2b) structure is the same as the 1e-(Format 3-2a)structure and may include L-fields in all the sub-headers. If in the1e-(Format 3-2a) structure, the size of the transport block (TB) isindicated by the L1 control signal, that is, the PDCCH even if the Lfield is not included in the last MAC sub-header as described above, thesize of the MAC PDU may be already known at the receiving side, andL-field values of the rest sub-headers may be confirmed at the receivingside and subtracted from the entire length of the MAC PDU to estimatethe length of the last MAC SDU. However, the above procedure is aprocedure that should receive the MAC PDU every time the terminalreceives the MAC PD. Therefore, the processing burden of the terminalmay be increased. Therefore, it may be advantageous to add the L fieldeven to the last MAC sub-header to reduce the processing burden of theterminal. As described above, the 1e-(Format 3-2b) structure ischaracterized in that an L field is added to the last sub-header inorder to lessen the processing burden of the terminal.

1e-(Format 3-2c) has a structure, such as a sub-header, a MAC CE, asub-header, a MAC SDU, a sub-header, and a padding and the first MAC PDUstructure has a repeating structure, such as a sub-header, a payload, asub-header, and a payload. The 1e-(Format 3-2c) structure is largelydivided into a MAC CE part and a MAC SDU part. The MAC CEs may belocated at the front part in the order in which they are firstgenerated, and in the MAC SDU part, segments of a MAC SDU (or RLC PDU orRLC SDU) may be located at the tail part of the MAC SDU part. In thiscase, the MAC CE may be a MAC CE associated with scheduling information,such as a buffer status report (BSR) and a power headroom report (PHR),and locating the generated MAC CEs at the head thereof as in the1e-(Format 3-2a) may be very advantageous in the scheduling of the basestation. For example, if the base station receives the MAC PDU from theterminal and first reads the MAC CEs associated with the schedulinginformation, the scheduling information may be directly provided to abase station scheduler to quickly schedule several terminals.

In addition, in this case, the MAC CEs may indicate various information.For example, there may be a kind of MAC CEs, such as a MAC CE indicatinginformation for several antenna configurations (FD-MIMO), a MAC CE (MACCE indicating how often or how many times the channel measurement isperformed or at which time/frequency transmission resource themeasurement and reporting are performed for the purpose of channel stateinformation-reference signal (CSI-RS), a sounding reference signal(SRS), a demodulated reference signal (DMRS), or the like) for channelmeasurement, a MAC CE (MAC CE used for the purpose of indicatingmobility of the terminal with L2 mobility, i.e., the MAC CE andindicating an inter-cell handover related instruction of the terminal)for quickly supporting the mobility of the terminal, a MAC CE (MAC CEindicating by which beam a service is received, the measurement isperformed, and information on the number of beams, time/frequencyresources of the beam, or the like) indicating beam-related informationrequired when the terminal performs camp on, random access, or cellmeasurement, a MAC CE (MAC CE (MAC CE indicating whether to use ShortTTI, whether to use general TTI (1 ms), or whether to use longer TTI, orthe like) dynamically indicating TTI to be used by the terminal, a MACCE (MAC CE indicating a dedicated transmission resource requesting SR tothe terminal) indicating information on the scheduling request (SR), anda MAC CE indicating transmission resource information/configurationinformation or the like required for the terminal supporting an URLLCservice.

The sub-header may include some of the variables described in Table 1,and information other than the variables described in Table 1. Thepadding is stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set theMAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 1e-(Format3-2c). For example, the header of the front part becomes the informationindicating the payload of the rear part. The 1e-(Format 3-2c) structureis characterized in that an L-field is not included in the lastsub-header. Since the size of the transport block (TB) is indicated bythe L1 control signal, that is, the PDCCH, the size of the MAC PDU maybe already known at the receiving side, and L-field values of the restsub-headers may be confirmed at the receiving side and subtracted fromthe entire length of the MAC PDU to estimate the length of the last MACSDU. In addition, in this case, if no segmentation occurs when the MACPDU is transmitted from the previous uplink transmission resource andthus no predetermined segment remains, a full MAC SDU is put from thefront part and if there is a MAC SDU larger than the uplink transmissionresource at the rear part, the segmentation may be performed and thesegment may be processed by being put in the rear part of the MAC SDUpart. By doing so, the receiving side can receive the RLC sequencenumber in order.

The 1e-(Format 3-2d) structure is the same as the 1e-(Format 3-2c)structure and may include L-fields in all the sub-headers. If in the1e-(Format 3-2c) structure, the size of the transport block (TB) isindicated by the L1 control signal, that is, the PDCCH even if the Lfield is not included in the last MAC sub-header as described above, thesize of the MAC PDU may be already known at the receiving side, andL-field values of the rest sub-headers may be confirmed at the receivingside and subtracted from the entire length of the MAC PDU to estimatethe length of the last MAC SDU. However, the above procedure is aprocedure that should receive the MAC PDU every time the terminalreceives the MAC PD. Therefore, the processing burden of the terminalmay be increased. Therefore, it may be advantageous to add the L fieldeven to the last MAC sub-header to reduce the processing burden of theterminal. As described above, the 1e-(Format 3-2d) structure ischaracterized in that an L field is added to the last sub-header inorder to lessen the processing burden of the terminal.

1e-(Format 3-2e) has a structure, such as a sub-header, a MAC CE, asub-header, a MAC SDU, a sub-header, and a padding and the first MAC PDUstructure has a repeating structure, such as a sub-header, a payload, asub-header, and a payload. The 1e-(Format 3-2e) structure is largelydivided into a MAC CE part and a MAC SDU part. The MAC CEs may belocated at a front part of the MAC SDU part in the order in which theyare first generated, and even the MAC CEs may be located at a rear partof the MAC CE part in the order in which they are first generated. Inthis case, the MAC CE may be dynamically generated for predeterminedreasons when the uplink transmission resource is allocated. For example,the case where after the uplink transmission resource is allocated andthe amount of data that may be currently transmitted is calculated, theamount of data that may be transmitted as the uplink transmissionresource is subtracted and the remaining amount of data to betransmitted at the next opportunity is reported to the buffer statusreport (BSR) may be considered as the example. A power head room (PHR)is one of other examples. For example, the PHR should be calculated andtransmitted at the time of receiving the uplink transmission resource.On the other hand, the MAC SDUs, that is, data are transmitted to a PDCPlayer, an RLC layer, and an MAC layer, and may be generated as an MACSDU together with the MAC sub-header.

Therefore, if the terminal is allocated the uplink transmissionresource, the MAC PDU is configured by first generated the MACsub-header and MAC SDUs generated in advance, and the MAC CE may begenerated simultaneously with constructing the MAC PDU. Theconfiguration of the MAC PDU may be completed by attaching the MAC CE tothe end of the MAC PDU. In this way, the operation of constructing theMAC PDU with the pre-generated MAC SDUs simultaneously with dynamicallygenerating the MAC CE is performed in parallel, thereby reducing theprocessing time of the terminal. For example, locating the MAC CE at therear part of the MAC PDU is advantageous in the processing time of theterminal.

In addition, in this case, the MAC CEs may indicate various information.For example, there may be a kind of MAC CEs, such as a MAC CE indicatinginformation for several antenna configurations (FD-MIMO), a MAC CE (MACCE indicating how often or how many times the channel measurement isperformed or at which time/frequency transmission resource themeasurement and reporting are performed for the purpose of channel stateinformation-reference signal (CSI-RS), a sounding reference signal(SRS), a demodulated reference signal (DMRS), or the like) for channelmeasurement, a MAC CE (MAC CE used for the purpose of indicatingmobility of the terminal with L2 mobility, i.e., the MAC CE andindicating an inter-cell handover related instruction of the terminal)for quickly supporting the mobility of the terminal, a MAC CE (MAC CEindicating by which beam a service is received, the measurement isperformed, and information on the number of beams, time/frequencyresources of the beam, or the like) indicating beam-related informationrequired when the terminal performs camp on, random access, or cellmeasurement, a MAC CE (MAC CE (MAC CE indicating whether to use ShortTTI, whether to use general TTI (1 ms), or whether to use longer TTI, orthe like) dynamically indicating TTI to be used by the terminal, a MACCE (MAC CE indicating a dedicated transmission resource requesting SR tothe terminal) indicating information on the scheduling request (SR), anda MAC CE indicating transmission resource information/configurationinformation or the like required for the terminal supporting an URLLCservice.

In the MAC SDU part, a last segment of one MAC SDU (or RLC PDU or RLCSDU) may be located at a head thereof and a first segment of one MAC SDU(or RLC PDU or RLC SDU) may be located at a tail thereof. The sub-headermay include some of the variables described in Table 1, and informationother than the variables described in Table 1. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the MAC PDU in byte units.In this case, each MAC sub-head indicates information corresponding toeach MAC SDU, MAC CE, and padding, in the order numbered on thesub-headers and the payloads of the 1e-(Format 3-2e). For example, theheader of the front part becomes the information indicating the payloadof the rear part. The 1e-(Format 3-2e) structure is characterized inthat an L-field is not included in the last sub-header. Since the sizeof the transport block (TB) is indicated by the L1 control signal, thatis, the PDCCH, the size of the MAC PDU may be already known at thereceiving side, and L-field values of the rest sub-headers may beconfirmed at the receiving side and subtracted from the entire length ofthe MAC PDU to estimate the length of the last MAC SDU. In this case, ifsegmentation is generated when the MAC PDU is transmitted in theprevious uplink transmission resource and thus a predetermined segmentremains, the remaining segments may be processed by being put in thefront part of the MAC SDU part. Therefore, the receiving side may firstreceive and re-assemble the data of the RLC PDU with the lowest RLCsequence number.

The 1e-(Format 3-2e) structure is the same as the 1e-(Format 3-2e)structure and may include L-fields in all the sub-headers. If in the1e-(Format 3-2e) structure, the size of the transport block (TB) isindicated by the L1 control signal, that is, the PDCCH even if the Lfield is not included in the last MAC sub-header as described above, thesize of the MAC PDU may be already known at the receiving side, andL-field values of the rest sub-headers may be confirmed at the receivingside and subtracted from the entire length of the MAC PDU to estimatethe length of the last MAC SDU. However, the above procedure is aprocedure that should receive the MAC PDU every time the terminalreceives the MAC PD. Therefore, the processing burden of the terminalmay be increased. Therefore, it may be advantageous to add the L fieldeven to the last MAC sub-header to reduce the processing burden of theterminal. As described above, the 1e-(Format 3-2f) structure ischaracterized in that an L field is added to the last sub-header inorder to lessen the processing burden of the terminal.

1e-(Format 3-2g) has a structure, such as a sub-header, a MAC CE, asub-header, a MAC SDU, a sub-header, and a padding and the first MAC PDUstructure has a repeating structure, such as a sub-header, a payload, asub-header, and a payload. The 1e-(Format 3-2g) structure is largelydivided into a MAC CE part and a MAC SDU part. The MAC CEs may belocated at a front part of the MAC SDU part in the order in which theyare first generated, and even the MAC CEs may be located at a rear partof the MAC CE part in the order in which they are first generated.

In this case, the MAC CE may be dynamically generated for predeterminedreasons when the uplink transmission resource is allocated. For example,the case where after the uplink transmission resource is allocated andthe amount of data that may be currently transmitted is calculated, theamount of data that may be transmitted as the uplink transmissionresource is subtracted and the remaining amount of data to betransmitted at the next opportunity is reported to the buffer statusreport (BSR) may be considered as the example. A power head room (PHR)is one of other examples. For example, the PHR should be calculated andtransmitted at the time of receiving the uplink transmission resource.On the other hand, the MAC SDUs, that is, data are transmitted to a PDCPlayer, an RLC layer, and an MAC layer, and may be generated as an MACSDU together with the MAC sub-header.

Therefore, if the terminal is allocated the uplink transmissionresource, the MAC PDU is configured by first generated the MACsub-header and MAC SDUs generated in advance, and the MAC CE may begenerated simultaneously with constructing the MAC PDU. Theconfiguration of the MAC PDU may be completed by attaching the MAC CE tothe end of the MAC PDU. In this way, the operation of constructing theMAC PDU with the pre-generated MAC SDUs simultaneously with dynamicallygenerating the MAC CE is performed in parallel, thereby reducing theprocessing time of the terminal. For example, locating the MAC CE at therear part of the MAC PDU is advantageous in the processing time of theterminal.

In addition, in this case, the MAC CEs may indicate various information.For example, there may be a kind of MAC CEs, such as a MAC CE indicatinginformation for several antenna configurations (FD-MIMO), a MAC CE (MACCE indicating how often or how many times the channel measurement isperformed or at which time/frequency transmission resource themeasurement and reporting are performed for the purpose of channel stateinformation-reference signal (CSI-RS), a sounding reference signal(SRS), a demodulated reference signal (DMRS), or the like) for channelmeasurement, a MAC CE (MAC CE used for the purpose of indicatingmobility of the terminal with L2 mobility, i.e., the MAC CE andindicating an inter-cell handover related instruction of the terminal)for quickly supporting the mobility of the terminal, a MAC CE (MAC CEindicating by which beam a service is received, the measurement isperformed, and information on the number of beams, time/frequencyresources of the beam, or the like) indicating beam-related informationrequired when the terminal performs camp on, random access, or cellmeasurement, a MAC CE (MAC CE (MAC CE indicating whether to use ShortTTI, whether to use general TTI (1 ms), or whether to use longer TTI, orthe like) dynamically indicating TTI to be used by the terminal, a MACCE (MAC CE indicating a dedicated transmission resource requesting SR tothe terminal) indicating information on the scheduling request (SR), anda MAC CE indicating transmission resource information/configurationinformation or the like required for the terminal supporting an URLLCservice.

In the MAC SDU part, the segments of one MAC SDU (or RLC PDU or RLC SDU)may be located at the tail. The sub-header may include some of thevariables described in Table 1, and information other than the variablesdescribed in Table 1. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the MAC PDU in byte units. In this case, each MACsub-head indicates information corresponding to each MAC SDU, MAC CE,and padding, in the order numbered on the sub-headers and the payloadsof the 1e-(Format 3-2g). For example, the header of the front partbecomes the information indicating the payload of the rear part. The1e-(Format 3-2g) structure is characterized in that an L-field is notincluded in the last sub-header. Since the size of the transport block(TB) is indicated by the L1 control signal, that is, the PDCCH, the sizeof the MAC PDU may be already known at the receiving side, and L-fieldvalues of the rest sub-headers may be confirmed at the receiving sideand subtracted from the entire length of the MAC PDU to estimate thelength of the last MAC SDU. In addition, in this case, if nosegmentation occurs when the MAC PDU is transmitted from the previousuplink transmission resource and thus no predetermined segment remains,a full MAC SDU is put from the front part and if there is a MAC SDUlarger than the uplink transmission resource at the rear, thesegmentation may be performed and the segment may be processed by beingput in the rear part of the MAC SDU part. By doing so, the receivingside can receive the RLC sequence number in order.

The 1e-(Format 3-2h) structure is the same as the 1e-(Format 3-2g)structure and may include L-fields in all the sub-headers. If in the1e-(Format 3-2g) structure, the size of the transport block (TB) isindicated by the L1 control signal, that is, the PDCCH even if the Lfield is not included in the last MAC sub-header as described above, thesize of the MAC PDU may be already known at the receiving side, andL-field values of the rest sub-headers may be confirmed at the receivingside and subtracted from the entire length of the MAC PDU to estimatethe length of the last MAC SDU. However, the above procedure is aprocedure that should receive the MAC PDU every time the terminalreceives the MAC PD. Therefore, the processing burden of the terminalmay be increased. Therefore, it may be advantageous to add the L fieldeven to the last MAC sub-header to reduce the processing burden of theterminal. As described above, the 1e-(Format 3-2h) structure ischaracterized in that an L field is added to the last sub-header inorder to lessen the processing burden of the terminal.

1e-(Format 3-2i) has a structure, such as a sub-header, a MAC CE, asub-header, a MAC SDU, a sub-header, and a padding and the first MAC PDUstructure has a repeating structure, such as a sub-header, a payload, asub-header, and a payload. The 1e-(Format 3-2i) structure is dividedinto a MAC CE part that may be first generated, a MAC SDU part, and aMAC CE part that are generated later. The MAC CEs may be located at afront part of the MAC SDU part in the order in which they are firstgenerated, and even the MAC CEs may be located at a rear part of the MACCE part in the order in which they are first generated. However, a MACCE (or the MAC CE determined to have the high priority, the MAC CE priorto the MAC SDU, or the MAC CE satisfying the predetermined criterion)that may be generated in advance before being allocated the uplinkresource of the uplink is the MAC CE part that may be generated firstand may be located at the head of the MAC PDU, and the remaining MAC CEsare the MAC CE part that may be generated later and may be located atthe tail of the MAC PDU.

In this case, the MAC CE may be a MAC CE associated with schedulinginformation, such as a buffer status report (BSR) and a power headroomreport (PHR), and locating the generated MAC CEs at the head thereof maybe very advantageous in the scheduling of the base station. For example,if the base station receives the MAC PDU from the terminal and firstreads the MAC CEs associated with the scheduling information, thescheduling information may be directly provided to a base stationscheduler to quickly schedule several terminals.

In addition, the MAC CE may be dynamically generated for predeterminedreasons when the uplink transmission resource is allocated. For example,the case where after the uplink transmission resource is allocated andthe amount of data that may be currently transmitted is calculated, theamount of data that may be transmitted as the uplink transmissionresource is subtracted and the remaining amount of data to betransmitted at the next opportunity is reported to the buffer statusreport (BSR) may be considered as the example. The power head room (PHR)is one of other examples. For example, the PHR should be calculated andtransmitted at the time of receiving the uplink transmission resource.On the other hand, the MAC SDUs, that is, data are transmitted to a PDCPlayer, an RLC layer, and an MAC layer, and may be generated as an MACSDU together with the MAC sub-header. Therefore, if the terminal isallocated the uplink transmission resource, the MAC PDU is configured byfirst generated the MAC sub-header and MAC SDUs generated in advance,and the MAC CE may be generated simultaneously with constructing the MACPDU. The configuration of the MAC PDU may be completed by attaching theMAC CE to the end of the MAC PDU. In this way, the operation ofconstructing the MAC PDU with the pre-generated MAC SDUs simultaneouslywith dynamically generating the MAC CE is performed in parallel, therebyreducing the processing time of the terminal. For example, locating theMAC CE at the rear part of the MAC PDU is advantageous in the processingtime of the terminal.

As described above, locating the MAC CE at the front part of the MAC PDUis advantageous in the scheduling of the base station, and locating theMAC CE at the rear part of the MAC PDU is advantageous in shortening theprocessing time of the terminal. Therefore, depending on theimplementation and if necessary, the MAC CE may be located before theMAC PDU or located after the MAC PDU.

In addition, in this case, the MAC CEs may indicate various information.For example, there may be a kind of MAC CEs, such as a MAC CE indicatinginformation for several antenna configurations (FD-MIMO), a MAC CE (MACCE indicating how often or how many times the channel measurement isperformed or at which time/frequency transmission resource themeasurement and reporting are performed for the purpose of channel stateinformation-reference signal (CSI-RS), a sounding reference signal(SRS), a demodulated reference signal (DMRS), or the like) for channelmeasurement, a MAC CE (MAC CE used for the purpose of indicatingmobility of the terminal with L2 mobility, i.e., the MAC CE andindicating an inter-cell handover related instruction of the terminal)for quickly supporting the mobility of the terminal, a MAC CE (MAC CEindicating by which beam a service is received, the measurement isperformed, and information on the number of beams, time/frequencyresources of the beam, or the like) indicating beam-related informationrequired when the terminal performs camp on, random access, or cellmeasurement, a MAC CE (MAC CE (MAC CE indicating whether to use ShortTTI, whether to use general TTI (1 ms), or whether to use longer TTI, orthe like) dynamically indicating TTI to be used by the terminal, a MACCE (MAC CE indicating a dedicated transmission resource requesting SR tothe terminal) indicating information on the scheduling request (SR), anda MAC CE indicating transmission resource information/configurationinformation or the like required for the terminal supporting an URLLCservice.

In the MAC SDU part, the last segment of one MAC SDU (or RLC PDU or RLCSDU) may be located at the head of the MAC SDU part and the firstsegment of one MAC SDU (or RLC PDU or RLC SDU) may be located at thetail of the MAC SDU part. The sub-header may include some of thevariables described in Table 1, and information other than the variablesdescribed in Table 1. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC CE,MAC SDU, and padding, in the order numbered on the sub-headers and thepayloads of the 1e-(Format 3-2i). For example, the header of the frontpart becomes the information indicating the payload of the rear part.The 1e-(Format 3-2i) structure is characterized in that an L-field isnot included in the last sub-header. Since the size of the transportblock (TB) is indicated by the L1 control signal, that is, the PDCCH,the size of the MAC PDU may be already known at the receiving side, andL-field values of the rest sub-headers may be confirmed at the receivingside and subtracted from the entire length of the MAC PDU to estimatethe length of the last MAC SDU. In this case, if segmentation isgenerated when the MAC PDU is transmitted in the previous uplinktransmission resource and thus a predetermined segment remains, theremaining segments may be processed by being put in the front part ofthe MAC SDU part. Therefore, the receiving side may first receive andre-assemble the data of the RLC PDU with the lowest RLC sequence number.

The 1e-(Format 3-2j) structure is the same as the 1e-(Format 3-2i)structure and may include L-fields in all the sub-headers. If in the1e-(Format 3-2i) structure, the size of the transport block (TB) isindicated by the L1 control signal, that is, the PDCCH even if the Lfield is not included in the last MAC sub-header as described above, thesize of the MAC PDU may be already known at the receiving side, andL-field values of the rest sub-headers may be confirmed at the receivingside and subtracted from the entire length of the MAC PDU to estimatethe length of the last MAC SDU. However, the above procedure is aprocedure that should receive the MAC PDU every time the terminalreceives the MAC PD. Therefore, the processing burden of the terminalmay be increased. Therefore, it may be advantageous to add the L fieldeven to the last MAC sub-header to reduce the processing burden of theterminal. As described above, the 1e-(Format 3-2j) structure ischaracterized in that an L field is added in order to lessen theprocessing burden of the terminal.

1e-(Format 3-2k) has a structure, such as a sub-header, a MAC CE, asub-header, a MAC SDU, a sub-header, and a padding and the first MAC PDUstructure has a repeating structure, such as a sub-header, a payload, asub-header, and a payload. The 1e-(Format 3-2k) structure is dividedinto a MAC CE part that may be first generated, a MAC SDU part, and aMAC CE part that are generated later. The MAC CEs may be located at afront part of the MAC SDU part in the order in which they are firstgenerated, and even the MAC CEs may be located at a rear part of the MACCE part in the order in which they are first generated. However, a MACCE (or the MAC CE determined to have the high priority, the MAC CE priorto the MAC SDU, or the MAC CE satisfying the predetermined criterion)that may be generated in advance before being allocated the uplinkresource of the uplink is the MAC CE part that may be generated firstand may be located at the head of the MAC PDU, and the remaining MAC CEsare the MAC CE part that may be generated later and may be located atthe tail of the MAC PDU.

In this case, the MAC CE may be a MAC CE associated with schedulinginformation, such as a buffer status report (BSR) and a power headroomreport (PHR), and locating the generated MAC CEs at the head thereof maybe very advantageous in the scheduling of the base station. For example,if the base station receives the MAC PDU from the terminal and firstreads the MAC CEs associated with the scheduling information, thescheduling information may be directly provided to a base stationscheduler to quickly schedule several terminals.

In addition, the MAC CE may be dynamically generated for predeterminedreasons when the uplink transmission resource is allocated. For example,the case where after the uplink transmission resource is allocated andthe amount of data that may be currently transmitted is calculated, theamount of data that may be transmitted as the uplink transmissionresource is subtracted and the remaining amount of data to betransmitted at the next opportunity is reported to the buffer statusreport (BSR) may be considered as the example. The power head room (PHR)is one of other examples. For example, the PHR should be calculated andtransmitted at the time of receiving the uplink transmission resource.On the other hand, the MAC SDUs, that is, data are transmitted to a PDCPlayer, an RLC layer, and an MAC layer, and may be generated as an MACSDU together with the MAC sub-header. Therefore, if the terminal isallocated the uplink transmission resource, the MAC PDU is configured byfirst generated the MAC sub-header and MAC SDUs generated in advance,and the MAC CE may be generated simultaneously with constructing the MACPDU. The configuration of the MAC PDU may be completed by attaching theMAC CE to the end of the MAC PDU. In this way, the operation ofconstructing the MAC PDU with the pre-generated MAC SDUs simultaneouslywith dynamically generating the MAC CE is performed in parallel, therebyreducing the processing time of the terminal. For example, locating theMAC CE at the rear part of the MAC PDU is advantageous in the processingtime of the terminal.

As described above, locating the MAC CE at the front part of the MAC PDUis advantageous in the scheduling of the base station, and locating theMAC CE at the rear part of the MAC PDU is advantageous in shortening theprocessing time of the terminal. Therefore, depending on theimplementation and if necessary, the MAC CE may be located before theMAC PDU or located after the MAC PDU.

In addition, in this case, the MAC CEs may indicate various information.For example, there may be a kind of MAC CEs, such as a MAC CE indicatinginformation for several antenna configurations (FD-MIMO), a MAC CE (MACCE indicating how often or how many times the channel measurement isperformed or at which time/frequency transmission resource themeasurement and reporting are performed for the purpose of channel stateinformation-reference signal (CSI-RS), a sounding reference signal(SRS), a demodulated reference signal (DMRS), or the like) for channelmeasurement, a MAC CE (MAC CE used for the purpose of indicatingmobility of the terminal with L2 mobility, i.e., the MAC CE andindicating an inter-cell handover related instruction of the terminal)for quickly supporting the mobility of the terminal, a MAC CE (MAC CEindicating by which beam a service is received, the measurement isperformed, and information on the number of beams, time/frequencyresources of the beam, or the like) indicating beam-related informationrequired when the terminal performs camp on, random access, or cellmeasurement, a MAC CE (MAC CE (MAC CE indicating whether to use ShortTTI, whether to use general TTI (1 ms), or whether to use longer TTI, orthe like) dynamically indicating TTI to be used by the terminal, a MACCE (MAC CE indicating a dedicated transmission resource requesting SR tothe terminal) indicating information on the scheduling request (SR), anda MAC CE indicating transmission resource information/configurationinformation or the like required for the terminal supporting an URLLCservice.

In the MAC SDU part, the segments of one MAC SDU (or RLC PDU or RLC SDU)may be located at the tail of the MAC SDU part. The sub-header mayinclude some of the variables described in Table 1, and informationother than the variables described in Table 1. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC CE, MAC SDU, and padding, in the ordernumbered on the sub-headers and the payloads of the 1e-(Format 3-2k).For example, the header of the front part becomes the informationindicating the payload of the rear part. The 1e-(Format 3-2k) structureis characterized in that an L-field is not included in the lastsub-header. Since the size of the transport block (TB) is indicated bythe L1 control signal, that is, the PDCCH, the size of the MAC PDU maybe already known at the receiving side, and L-field values of the restsub-headers may be confirmed at the receiving side and subtracted fromthe entire length of the MAC PDU to estimate the length of the last MACSDU. In addition, in this case, if no segmentation occurs when the MACPDU is transmitted from the previous uplink transmission resource andthus no predetermined segment remains, a full MAC SDU is put from thefront part and if there is a MAC SDU larger than the uplink transmissionresource at the rear part, the segmentation may be performed and thesegment may be processed by being put in the rear part of the MAC SDUpart. By doing so, the receiving side can receive the RLC sequencenumber in order.

The 1e-(Format 3-2l) structure is the same as the 1e-(Format 3-2k)structure and may include L-fields in all the sub-headers. If in the1e-(Format 3-2k) structure, the size of the transport block (TB) isindicated by the L1 control signal, that is, the PDCCH even if the Lfield is not included in the last MAC sub-header as described above, thesize of the MAC PDU may be already known at the receiving side, andL-field values of the rest sub-headers may be confirmed at the receivingside and subtracted from the entire length of the MAC PDU to estimatethe length of the last MAC SDU. However, the above procedure is aprocedure that should receive the MAC PDU every time the terminalreceives the MAC PD. Therefore, the processing burden of the terminalmay be increased. Therefore, it may be advantageous to add the L fieldeven to the last MAC sub-header to reduce the processing burden of theterminal. As described above, the 1e-(Format 3-2l) structure ischaracterized in that an L field is added in order to lessen theprocessing burden of the terminal.

FIG. 1F is a diagram illustrating a first MAC sub-header structuresuitable for a first MAC PDU structures for a next generation mobilecommunication system according to an embodiment of the presentdisclosure.

Referring to FIG. 1F, the first MAC sub-header structure includes a5-bit logical channel identity (LCID) field and an 11-bit length (L)field as in 1 f-05. The LCID field is used to identify logical channelsfrom different RLC apparatus, and the L field serves to indicate thesize of the MAC SDU. In this case, since the L field has a size of 11bits, the size of a MAC SDU (RLC PDU) may have a size from 1 byte to2048 bytes. The reason why the length of the L field is 11 bits is thatthe size of the general IP packet is 1500 bytes. To support this, the11-bit length is required (10 bits may indicate up to 1024 bytes, andtherefore may not indicate 1500 bytes). Therefore, the maximum size ofthe RLC SDU of each logical channel is the size of 2048—RLC header, andthe maximum size of the PDCP SDU of each logical channel is 2048—RLCheader size—PDCP header size. Since the maximum size of each RLC PDUthat may be supported by the 11-bit L field of the first MAC sub-headeris 2048 bytes, if the size of the RLC PDU is larger than 2048 bytes, thesegmentation is performed in the RLC layer to segment the RLC PDU into asize smaller than 2048 bytes. For example, the segmentation may be firstperformed according to the size of the RLC PDU (or IP packet) before thetransmission resource is allocated. The MAC sub-header structure may becharacterized in that there is no E field described in the aboveTable 1. Since the structure of the MAC PDU described in FIGS. 1EA to1EC is the structure in which the MAC SDU is always present after theMAC sub-header, the E field is not required.

FIG. 1G is a diagram illustrating a second MAC sub-header structuresuitable for a first MAC PDU structures for a next generation mobilecommunication system according to an embodiment of the presentdisclosure.

Referring to FIG. 1G, the second MAC sub-header structure includes a1-bit reserved (R) field, a 4-bit logical channel identity (LCID) field,and an 11-bit length (L) field as in 1 g-05. The R field is a reservedfield, the LCID field used to identify logical channels from differentRLC apparatus, and the L field serves to indicate the size of the MACSDU. In this case, all the MAC CEs can be indicated by one LCID, and aCE type field indicating each MAC CE can be separately provided in theMAC SDU. For example, when the LCID indicates the MAC CE, predeterminedbits (CE type field) at the head of the MAC SDU may be used to indicatedifferent MAC CEs. If the predetermined bits (CE type field) are 3 bits,they may indicate {circumflex over ( )}3=8 different MAC CEs. In thiscase, since the L field has a size of 11 bits, the size of a MAC SDU(RLC PDU) may have a size from 1 byte to 2048 bytes. The reason why thelength of the L field is 11 bits is that the size of the general IPpacket is 1500 bytes. To support this, the 11-bit length is required (10bits may indicate up to 1024 bytes, and therefore may not indicate 1500bytes). Therefore, the maximum size of the RLC SDU of each logicalchannel is the size of 2048—RLC header, and the maximum size of the PDCPSDU of each logical channel is 2048—RLC header size—PDCP header size.Since the maximum size of each RLC PDU that may be supported by the11-bit L field of the second MAC sub-header is 2048 bytes, if the sizeof the RLC PDU is larger than 2048 bytes, the segmentation is performedin the RLC layer to segment the RLC PDU into a size smaller than 2048bytes. For example, the segmentation may be first performed according tothe size of the RLC PDU (or IP packet) before the transmission resourceis allocated. The MAC sub-header structure may be characterized in thatthere is no E field described in the above Table 1. Since the structureof the MAC PDU described in FIGS. 1EA, 1EB, and 1EC is the structure inwhich the MAC SDU is always present after the MAC sub-header, the Efield is not required.

The second MAC sub-header structure may be useful when having variousMAC CEs in the next generation mobile communication system. For example,if many types of MAC CEs need to be defined, they all may be difficultto be mapped to LCIDs. Therefore, the MAC CE type field may be definedin the payload part of the MAC CE to indicate many types of MAC CEs.Examples that may be defined as the useful MAC in the next generationmobile communication system are as follows.

In this case, the MAC CEs can be defined for various purposes. Forexample, there may be a kind of MAC CEs, such as a MAC CE indicatinginformation for several antenna configurations (FD-MIMO), a MAC CE (MACCE indicating how often or how many times the channel measurement isperformed or at which time/frequency transmission resource themeasurement and reporting are performed for the purpose of channel stateinformation-reference signal (CSI-RS), a sounding reference signal(SRS), a demodulated reference signal (DMRS), or the like) for channelmeasurement, a MAC CE (MAC CE used for the purpose of indicatingmobility of the terminal with L2 mobility, i.e., the MAC CE andindicating an inter-cell handover related instruction of the terminal)for quickly supporting the mobility of the terminal, a MAC CE (MAC CEindicating by which beam a service is received, the measurement isperformed, and information on the number of beams, time/frequencyresources of the beam, or the like) indicating beam-related informationrequired when the terminal performs camp on, random access, or cellmeasurement, a MAC CE (MAC CE (MAC CE indicating whether to use ShortTTI, whether to use general TTI (1 ms), or whether to use longer TTI, orthe like) dynamically indicating TTI to be used by the terminal, a MACCE (MAC CE indicating a dedicated transmission resource requesting SR tothe terminal) indicating information on the scheduling request (SR), anda MAC CE indicating transmission resource information/configurationinformation or the like required for the terminal supporting an URLLCservice.

FIG. 1H is a diagram illustrating a third MAC sub-header structuresuitable for a first MAC PDU structures for a next generation mobilecommunication system according to an embodiment of the presentdisclosure.

Referring to FIG. 1H, the third MAC sub-header structure may have astructure of two MAC sub-headers, in as 1 h-05 and 1 h-10. The 1 h-05 isa 3-1-th MAC sub-header structure and includes a 1-bit reserved R field,a 5-bit logical channel identity (LCID) field, and a 10-bit length (L)field. In the above field, the R field is a reserved field, the LCIDfield used to identify logical channels from different RLC apparatus,and the L field serves to indicate the size of the MAC SDU. In thestructure for allocating the reserved bit (R field) to be used in thefuture as described above, the L field has naturally 10 bits. The reasonis that the MAC sub-header structure is a byte-aligned structure. Inother words, since the sub-header needs to be configured in units ofbytes, the L field naturally has a 10-bit length except for a 1-bit Rfield and a 5-bit LCID field. The MAC sub-header structure may becharacterized in that there is no E field described in the aboveTable 1. Since the structure of the MAC PDU described in FIGS. 1EA, 1EB,and 1EC is the structure in which the MAC SDU is always present afterthe MAC sub-header, the E field is not required.

The 1 h-10 is a 3-2-th MAC sub-header structure and includes a 1-bitreserved R field, a 5-bit logical channel identity (LCID) field, and an18-bit length (L) field. In the structure for allocating the reservedbit (R field) to be used in the future as described above, the L fieldhas naturally 10 bits or 18 bits. The reason is that the MAC sub-headerstructure is a byte-aligned structure. In other words, since thesub-header needs to be configured in units of bytes, the L fieldnaturally has a 10-bit length except for a 1-bit R field and a 5-bitLCID field. If a longer L field is intended to be defined, it naturallyhas an 18-bit L field. In this case, the reason why the longer L fieldis required is that in order to support a jumbo IP packet having a sizeof 9000 bytes or a super jumbo IP packet having a very large size of36000/64000 bytes in addition to the general IP packet having a size of1500 bytes, the L field having a long length like the 18-bit length isrequired. The MAC sub-header structure may be characterized in thatthere is no E field described in the above Table 1. Since the structureof the MAC PDU described in FIGS. 1EA, 1EB, and 1EC is the structure inwhich the MAC SDU is always present after the MAC sub-header, the Efield is not required.

The third MAC sub-header structure may apply a 3-1-th MAC sub-headerstructure or a 3-2-th MAC sub-header structure depending on the size ofthe MAC SDU (RLC PDU). Since the 3-1-th MAC sub-header structure uses a10-bit L field, it may indicate a size from 1 byte to 1024 bytes, and inthe 3-2-th MAC sub-header structure, 18 bits may indicate a size from 1byte to 262144 bytes.

In the third MAC sub-header structure, which of the 3-1-th a 3-2-th MACsub-header structures is used may be determined by being promised inadvance for each LCID. Alternatively, it may be defined for each size ofthe MAC PDUs (because the size of the transport block is indicated bythe control signal in the physical layer, it may appreciate the size ofthe MAC PDU) or a 1 bit (in-band field) may be defined in the MAC SDU toindicate the 3-1-th or 3-2-th MAC sub-header structure. Alternatively,the R field of the MAC sub-header may be newly defined to indicate the3-1-th or 3-2-th MAC sub-header structure. Unlike the first and secondMAC sub-header structures, the third MAC sub-header structure maysupport a size up to 262144 bytes, and therefore, the segmentation maynot be first performed in the RLC layer before being allocated thetransmission resource.

FIG. 1I is a diagram illustrating an operation of a terminal related toa method for applying a MAC sub-header according to an embodiment of thepresent disclosure.

Referring to FIG. 1I, if the terminal 1 i-01 satisfies the firstcondition in operation 1 i-05, the operation of the terminal proceeds tooperation 1 i-10 and thus the segmentation is performed in the RLClayer, and each segment is transferred to the MAC layer to generate theMAC sub-headers of each segment. If the first condition is not satisfiedin operation 1 i-05, the operation of the terminal proceeds to operation1 i-15 to transfer the corresponding RLC PDU to the MAC layer andgenerate the MAC sub-header. In this case, the first condition may be acondition that the size of the RLC PDU (or RLC SDU) is larger than apredetermined size. For example, it may be a condition for confirmingthat the size of the RLC PDU is larger than 2048 bytes.

FIG. 1J is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure.

Referring to FIG. 1J, the terminal includes a radio frequency (RF)processor 1 j-10, a baseband processor 1 j-20, a storage 1 j-30, and acontroller 1 j-40.

The RF processor 1 j-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 1 j-10 up-converts a baseband signalprovided from the baseband processor 1 j-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 1 j-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, adigital to analog converter (DAC), an analog to digital converter (ADC),or the like. FIG. 1J illustrates only one antenna but the terminal mayinclude a plurality of antennas. Further, the RF processor 1 j-10 mayinclude a plurality of RF chains. Further, the RF processor 1 j-10 mayperform beamforming. For the beamforming, the RF processor 1 j-10 mayadjust a phase and a size of each of the signals transmitted andreceived through a plurality of antennas or antenna elements. Inaddition, the RF processor 1210 may perform MIMO and may receive aplurality of layers when performing the MIMO operation. The RF processor1 j-10 may perform reception beam sweeping by appropriately configuringa plurality of antennas or antenna elements under the control of thecontroller or adjust a direction and a beam width of the reception beamso that the reception beam is resonated with the transmission beam.

The baseband processor 1 j-20 performs a conversion function between abaseband signal and a bit string according to a physical layer standardof a system. For example, when data are transmitted, the basebandprocessor 1 j-20 generates complex symbols by coding and modulating atransmitted bit string. Further, when data are received, the basebandprocessor 1 j-20 recovers the received bit string by demodulating anddecoding the baseband signal provided from the RF processor 1 j-10. Forexample, according to the OFDM scheme, when data are transmitted, thebaseband processor 1 j-20 generates the complex symbols by coding andmodulating the transmitting bit string, maps the complex symbols tosub-carriers, and then performs an inverse fast Fourier transform (IFFT)operation and a cyclic prefix (CP) insertion to construct the OFDMsymbols. Further, when data are received, the baseband processor 1 j-20divides the baseband signal provided from the RF processor 1 j-10 in anOFDM symbol unit and recovers the signals mapped to the sub-carriers bya fast Fourier transform (FFT) operation and then recovers the receivedbit string by the modulation and decoding.

The baseband processor 1 j-20 and the RF processor 1 j-10 transmit andreceive a signal as described above. Therefore, the baseband processor 1j-20 and the RF processor 1 j-10 may be called a transmitter, areceiver, a transceiver, or a communication unit. Further, at least oneof the baseband processor 1 j-20 and the RF processor 1 j-10 may includea plurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 1 j-20 and the RF processor 1 j-10 may include differentcommunication modules to process signals in different frequency bands.For example, the different wireless access technologies may include anLTE network, an NR network, and the like. Further, different frequencybands may include a super high frequency (SHF) (for example: 2.5 GHz, 5GHz) band, a millimeter wave (for example: 60 GHz) band.

The storage 1 j-30 stores data, such as basic programs, applicationprograms, and configuration information for the operation of theterminal. Further, the storage 1 j-30 provides the stored data accordingto the request of the controller 1 j-40.

The controller 1 j-40 includes a multiple connection processor 1 j-42and controls the overall operations of the terminal. For example, thecontroller 1 j-40 transmits and receives a signal through the basebandprocessor 1 j-20 and the RF processor 1 j-10. Further, the controller 1j-40 records and reads data in and from the storage 1 j-30. For thispurpose, the controller 1 j-40 may include at least one processor. Forexample, the controller 1 j-40 may include a communication processor(CP) performing a control for communication and an application processor(AP) controlling an upper layer, such as the application programs.

FIG. 1K is a block configuration diagram of TRP in a wirelesscommunication system according to an embodiment of the presentdisclosure.

Referring to FIG. 1K, the base station is configured to include an RFprocessor 1 k-10, a baseband processor 1 k-20, a communication unit 1k-30, a storage 1 k-40, and a controller 1 k-50.

The RF processor 1 k-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 1 k-10 up-converts a baseband signalprovided from the baseband processor 1 k-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 1 k-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC,an ADC, or the like. FIG. 1K illustrates only one antenna but the firstaccess node may include a plurality of antennas. Further, the RFprocessor 1 k-10 may include a plurality of RF chains. Further, the RFprocessor 1 k-10 may perform the beamforming. For the beamforming, theRF processor 1 k-10 may adjust a phase and a size of each of the signalstransmitted/received through a plurality of antennas or antennaelements. The RF processor may perform a downward MIMO operation bytransmitting one or more layers.

The baseband processor 1 k-20 performs a conversion function between thebaseband signal and the bit string according to the physical layerstandard of the first radio access technology. For example, when dataare transmitted, the baseband processor 1 k-20 generates complex symbolsby coding and modulating a transmitted bit string. Further, when dataare received, the baseband processor 1 k-20 recovers the received bitstring by demodulating and decoding the baseband signal provided fromthe RF processor 1 k-10. For example, according to the OFDM scheme, whendata are transmitted, the baseband processor 1 k-20 generates thecomplex symbols by coding and modulating the transmitting bit string,maps the complex symbols to the sub-carriers, and then performs the IFFToperation and the CP insertion to construct the OFDM symbols. Further,when data are received, the baseband processor 1 k-20 divides thebaseband signal provided from the RF processor 1 k-10 in the OFDM symbolunit and recovers the signals mapped to the sub-carriers by the FFToperation and then recovers the receiving bit string by the modulationand decoding. The baseband processor 1 k-20 and the RF processor 1 k-10transmit and receive a signal as described above. Therefore, thebaseband processor 1 j-20 and the RF processor 1 j-10 may be called atransmitter, a receiver, a transceiver, or a communication unit.

The communication unit 1 k-30 provides an interface for performingcommunication with other nodes within the network.

The storage 1 k-40 stores data, such as basic programs, applicationprograms, and configuration information for the operation of the mainbase station. More particularly, the storage 1 k-40 may store theinformation on the bearer allocated to the accessed terminal, themeasured results reported from the accessed terminal, and the like.Further, the storage 1 k-40 may store information that is adetermination criterion on whether to provide a multiple connection tothe terminal or stop the multiple connection to the terminal. Further,the storage 1 k-40 provides the stored data according to the request ofthe controller 1 k-50.

The controller 1 k-50 includes a multiple connection processor 1 k-52and controls the general operations of the main base station. Forexample, the controller 1 k-50 transmits/receives a signal through thebaseband processor 1 k-20 and the RF processor 1 k-10 or thecommunication unit 1 k-30. Further, the controller 1 k-50 records andreads data in and from the storage 1 k-40. For this purpose, thecontroller 1 k-50 may include at least one processor.

FIG. 1L is a diagram illustrating detailed devices of a terminalaccording to an embodiment of the present disclosure.

Referring to FIG. 1L, the terminal may have the PDCP apparatus 1 l-05and the RLC apparatus 1 l-10 for each logical channel. If IP packets areinput from an upper layer or the apparatus to the PDCP apparatus, thePDCP apparatus compresses and ciphers a header of the IP packet,attaches the PDCP heater to the compressed and ciphered header of the IPpacket, and transfers the PDCP PDU to the RLC apparatus. In this case,the PDCP apparatus can process several IP packets at the same time andtransfer a plurality of PDCP PDUs to the RLC apparatus in parallel. Inan embodiment of the present disclosure, the RLC apparatus may processthe PDCP PDU in advance and transmit the processed PDCP PDU to the MACapparatus even if the terminal does not receive the uplink transmissionresource (UL grant) (pre-processing). In this case, an RLC controller 1l-12 of the RLC apparatus determines the size of the PDCP PDU and mayinstruct an RLC segmentation and reassembly unit to perform thesegmentation if it is determined that it is impossible to support thePDCP PDU by the length of the L field supported by the MAC apparatus.For example, if the L field supports 11 bits in the MAC apparatus, thesize up to 2048 bytes may be indicated and therefore if the size of theRLC header and the RLC SDU (PDCP PDU) is 4000 bytes, the RLC controller1 l-12 instructs the RLC segmentation and assembly unit 1 l-14 toperform the segmentation and may generate an RLC PDU having 2048 bytesand an RLC PDU having the rest bytes obtained by subtracting 2048 bytesfrom 4000 bytes and transfer the RLC PDUs to the MAC apparatus. In thiscase, the RLC apparatus can process several PDCP PDUs at the same timeand transfer several RLC PDUs to the MAC apparatus in parallel. When theMAC apparatus 1 l-20 receive the RLC PDUs from the RLC apparatus ofdifferent logical channels, the MAC controller 1 l-20 of the MACapparatus instructs a multiplexer 1 l-30 or other devices 1 l-40 topreviously construct the MAC sub-headers and the MAC SDUs for eachlogical channel and pre-process the pre-configured MAC sub-headers andMAC SDUs in a buffer 1 l-45. In this case, the sizes of MAC sub-headersand the MAC SDUs that may be configured in advance for each logicalchannel may be equal to the size of the maximum transport block (TB). Inthis case, the MAC apparatus requests scheduling to the base station,transmits the buffer status report (BSR), and receives the uplinktransmission resources in order to transmit data. In this case, if theMAC apparatus of the terminal receives the uplink transmission resource,the MAC apparatus determines the size of the uplink transmissionresource, and the MAC controller 1 l-25 may instruct a logical channelprioritization (LCP) device 1 l-35 to perform and LCP procedure andallocate the transmission resource to each logical channel. Then, theMAC controller 1 l-25 instructs the multiplexer 1 l-30 to multiplex theMAC sub-headers and the MAC SDUs previously configured for each logicalchannel in order according to the sizes of the transmission resourcesallocated for each logical channel. If the sizes of the MAC sub-headersand the MAC SDUs configured in advance are larger than the transmissionresources allocated to a certain logical channel, the MAC controller 1l-25 may request the RLC controller 1 l-2 to segment the correspondingRLC PDU. Then, the RLC controller 1 l-12 requests the RLC segmentationand assembly unit 1 l-14 to segment the corresponding RLC PDU andtransfers the segmented and newly configured RLC PDUs to the MACapparatus, and the MAC apparatus may again construct MAC sub-headers toconstruct MAC sub-headers and MAC SDUs according to the transmissionresources of each logical channel, thereby completing the configurationof the MAC PDU The MAC apparatus first may transmit the MAC sub-headerand the MAC SDU configured from the front of the MAC PDU to the PHYdevice 1 l-50 and first perform the processing of the PHY device. Thereceiving end may first transmit the MAC sub-header and the MAC SDUfirst processed from the front of the MAC PDU by the MAC apparatus 1l-20 to the RLC apparatus 1 l-10 to first perform the processing of theRLC apparatus. In this case, the MAC apparatus may simultaneouslyprocess several MAC sub-headers and MAC SDUs in parallel, andsimultaneously transmit a plurality of MAC sub-headers and MAC SDUs tothe PHY device or the RLC apparatus in parallel.

FIGS. 1MA and 1MB are diagrams illustrating in a time sequence a processof constructing MAC sub-headers and MAC SDUs in advance before aterminal is allocated a transmission resource, constructing an MAC PDUby generating an MAC CE simultaneously with constructing an MAC PDUconsisting of the MAC sub-headers and MAC SDUs generated in advance ifan uplink transmission resource is allocated, and locating the MAC CE atan end of the MAC PDU according to embodiments of the presentdisclosure.

Referring to FIGS. 1MA and 1MB, if the terminal inputs IP packets fromthe upper layer or the apparatus for each logical channel 1 m-05 and 1m-10 to the PDCP apparatus, the PDCP apparatus compresses and ciphersthe header of the IP packet and then attach the PDCP heater thereto andtransfers the PDCP PDU to the RLC apparatus. In this case, the PDCPapparatus may process several IP packets at the same time and transfer aplurality of PDCP PDUs to the RLC apparatus in parallel. In anembodiment of the present disclosure, the RLC apparatus may process thePDCP PDU in advance and transmit the processed PDCP PDU to the MACapparatus even if the terminal does not receive the uplink transmissionresource (UL grant) (pre-processing). For example, the RLC PDU iscreased immediately to be transferred to the MAC apparatus (Time 0). Inthis case, the RLC apparatus can process several PDCP PDUs at the sametime and transfer several RLC PDUs to the MAC apparatus in parallel. Ifthe MAC apparatus receives the RLC PDUs from the RLC apparatus of thedifferent logical channels (Time 0), it can pre-construct the MACsub-headers and the MAC SDUs for each logical channel and store them ina buffer (pre-processing, 1 m-15, 1 m-20). The MAC apparatus may requestthe scheduling to the base station, transmit the buffer status report(BSR), and may be allocated the uplink transmission resources in orderto transmit data. In this case, if the MAC apparatus of the terminalreceives the uplink transmission resource, it can determine its size,perform a logical channel prioritization (LCP) procedure, and allocatetransmission resources for each logical channel (1 m-25, 1 m-30, Time2). Then, the MAC apparatus may multiplex the MAC sub-headers and theMAC SDUs previously configured for each logical channel in orderaccording to the size of the transmission resources allocated for eachlogical channel (1 m-35, 40). If the sizes of the MAC sub-headers andthe MAC SDUs configured in advance are larger than the transmissionresources allocated to a certain logical channel, the MAC apparatus mayrequest the RLC apparatus to segment the corresponding RLC PDU. Then,the RLC apparatus segments the corresponding RLC PDU and transfers thenewly configured RLC PDUs to the MAC apparatus, and the MAC apparatusconfigures the MAC sub-headers again to construct the MAC sub-headersand the MAC SDUs according to the transmission resources of each logicalchannel, thereby completing the configuration of the MAC PDU (1 m-35, 1m-40, and 1 m-50). If there are predetermined reasons for the MAC CE tobe generated (for example, if another MAC CE is to be transmittedaccording to the instruction of the BSR, PHR, or RRC layer), the MACapparatus generate the MAC CEs in parallel simultaneously withconstructing the MAC PDU by the MAC sub-headers and the MAC SDUs (1 m-45and 1 m-40), thereby reducing the processing time (1 m-45). If thepreparation is completed at Time 3, the MAC sub-headers and the MAC SDUsare multiplexed in order, and the MAC CE is put in the end, therebycompleting the MAC PDU (1 m-45).

FIGS. 1NA and 1NB are diagrams illustrating in a time sequence a processof constructing MAC sub-headers and MAC SDUs in advance before aterminal is allocated a transmission resource, constructing an MAC PDUby generating an MAC CE simultaneously with constructing an MAC PDUconsisting of the MAC sub-headers and MAC SDUs generated in advance ifan uplink transmission resource is allocated, and locating the MAC CE atan end of the MAC PDU according to embodiments of the presentdisclosure.

Referring to FIGS. 1NA and 1NB, if the terminal inputs IP packets fromthe upper layer or the apparatus for each logical channel 1 n-05 and 1n-10 to the PDCP apparatus, the PDCP apparatus compresses and ciphersthe header of the IP packet and then attach the PDCP heater thereto andtransfers the PDCP PDU to the RLC apparatus. In this case, the PDCPapparatus may process several IP packets at the same time and transfer aplurality of PDCP PDUs to the RLC apparatus in parallel. In anembodiment of the present disclosure, the RLC apparatus may process thePDCP PDU in advance and transmit the processed PDCP PDU to the MACapparatus even if the terminal does not receive the uplink transmissionresource (UL grant) (pre-processing). For example, the RLC PDU may beimmediately generated to be transferred to the MAC apparatus (Time 0).In this case, the RLC apparatus can process several PDCP PDUs at thesame time and transfer several RLC PDUs to the MAC apparatus inparallel. If the MAC apparatus receives the RLC PDUs from the RLCapparatus of the different logical channels (Time 0), it canpre-construct the MAC sub-headers and the MAC SDUs for each logicalchannel and store them in a buffer (pre-processing, 1 m-15, 1 m-20). TheMAC apparatus may request the scheduling to the base station, transmitthe buffer status report (BSR), and may be allocated the uplinktransmission resources in order to transmit data. In this case, if theMAC apparatus of the terminal receives the uplink transmission resource,it can determine its size, perform a logical channel prioritization(LCP) procedure, and allocate transmission resources for each logicalchannel (1 n-25, 1 n-30, Time 2). Then, the MAC apparatus may multiplexthe MAC sub-headers and the MAC SDUs previously configured for eachlogical channel in order according to the size of the transmissionresources allocated for each logical channel (1 n-35, 40). If the sizesof the MAC sub-headers and the MAC SDUs configured in advance are largerthan the transmission resources allocated to a certain logical channel,the MAC apparatus may request the RLC apparatus to segment thecorresponding RLC PDU. Then, the RLC apparatus segments thecorresponding RLC PDU and transfers the newly configured RLC PDUs to theMAC apparatus, and the MAC apparatus configures the MAC sub-headersagain to construct the MAC sub-headers and the MAC SDUs according to thetransmission resources of each logical channel, thereby completing theconfiguration of the MAC PDU (1 n-35, 1 n-40, and 1 n-50). If there ispredetermined reasons for the MAC CE to be generated (for example, ifanother MAC CE is to be transmitted according to the instruction of theBSR, PHR, or RRC layer), the MAC apparatus generate the MAC CEs inparallel simultaneously with constructing the MAC PDU with the MACsub-headers and the MAC SDUs (1 n-35 and 1 n-40), thereby reducing theprocessing time (1 n-45). If the preparation is completed at time 3, theMAC CE is put in the head, and the base station first confirms the MACCE and quickly obtains the scheduling information to quickly obtain thescheduling information of the terminals, and then multiplexes the MACsub-headers and the MAC SDUs in order, thereby completing the MAC PDU (1n-50).

FIGS. 10A and 10B are diagrams illustrating in a time sequence a processof constructing MAC sub-headers and MAC SDUs in advance before aterminal is allocated a transmission resource, constructing an MAC PDUby generating an MAC CE simultaneously with constructing an MAC PDUconsisting of the MAC sub-headers and MAC SDUs generated in advance ifan uplink transmission resource is allocated, and locating the MAC CE atan end of the MAC PDU according to embodiments of the presentdisclosure.

FIGS. 10A and 10B may perform the same procedures as those of FIGS. 1NAand 1NB. However, if the MAC sub-headers and the MAC SDUs are preparedbefore the MAC CE is generated, the place where the MAC CE is to beconfigured is left at the head like 1 o-50 (in practice, the memorywhose the head part is filled with the MAC CE is reserved in advance)and the configuration of the MAC PDU may start with the prepared MACsub-headers and the MAC SDUs from the back thereof. If the generation ofthe MAC CE is completed, the MAC CE may be located at the head of theMAC PDU that was previously left or reserved.

Second Embodiment

FIG. 2A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure.

Referring to FIG. 2A, a radio access network of an LTE system isconfigured to include next generation base stations (evolved node B,hereinafter, eNB, Node B, or base station) 2 a-05, 2 a-10, 2 a-15, and 2a-20, a mobility management entity (MME) 2 a-25, and a serving-gateway(S-GW) 2 a-30. User equipment (hereinafter, UE or terminal) 2 a-35accesses an external network through the eNBs 2 a-05 to 2 a-20 and theS-GW 2 a-30.

Referring to FIG. 2A, the eNB 2 a-05 to 2 a-20 correspond to theexisting node B of the UMTS system. In the LTE system, in addition to areal-time service like a voice over Internet protocol (VoIP) through theInternet protocol, all the user traffics are served through a sharedchannel and therefore an apparatus for collecting and scheduling statusinformation, such as a buffer status, an available transmit powerstatus, and a channel state of the terminals is required. Here, the eNBs2 a-05 to 2 a-20 take charge of the collecting and scheduling. The eNBis connected to the UE 2 a-35 through a radio channel and performs morecomplicated role than the existing node B. For example, to implement atransmission rate of 100 Mbps, the LTE system uses, as a radio accesstechnology, OFDM, for example, in a bandwidth of 20 MHz. Further, anadaptive modulation & coding (hereinafter, called AMC) determining amodulation scheme and a channel coding rate depending on the channelstatus of the terminal is applied. The S-GW 2 a-30 is an apparatus forproviding a data bearer and generates or removes the data beareraccording to the control of the MME 2 a-25. The MME is an apparatus forperforming a mobility management function for the terminal and variouscontrol functions and is connected to a plurality of base stations.

FIG. 2B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure.

Referring to FIG. 2B, the radio protocol of the LTE system is configuredto include PDCPs 2 b-05 and 2 b-40, RLCs 2 b-10 and 2 b-35, and mediumaccess controls (MMCs) 2 b-15 and 2 b-30 in the terminal and the eNB,respectively. The PDCPs 2 b-05 and 2 b-40 are in charge of operations,such as IP header compression/decompression. The main functions of thePDCP are summarized as follows.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUsat PDCP re-establishment procedure for RLC AM)

Reordering function (For split bearers in DC (only support for RLC AM):PDCP PDU routing for transmission and PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs atPDCP re-establishment procedure for RLC AM)

Retransmission function (Retransmission of PDCP SDUs at handover and,for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure,for RLC AM)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink.)

The RLCs 2 b-10 and 2 b-35 reconfigures the PDCP PDU to an appropriatesize to perform the ARQ operation or the like. The main functions of theRLC are summarized as follows.

Data transfer function (Transfer of upper layer PDUs)

ARQ function (Error Correction through ARQ (only for AM data transfer))

Concatenation, segmentation, reassembly functions (Concatenation,segmentation and reassembly of RLC SDUs (only for UM and AM datatransfer))

Re-segmentation function (Re-segmentation of RLC data PDUs (only for AMdata transfer))

Reordering function (Reordering of RLC data PDUs (only for UM and AMdata transfer)

Duplicate detection function (Duplicate detection (only for UM and AMdata transfer))

Error detection function (Protocol error detection (only for AM datatransfer))

RLC SDU discard function (RLC SDU discard (only for UM and AM datatransfer))

RLC re-establishment function (RLC re-establishment)

The MACs 2 b-15 and 2 b-30 are connected to several RLC layer apparatusconfigured in one terminal and perform an operation of multiplexing RLCPDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU.The main functions of the MAC are summarized as follows.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MACSDUs belonging to one or different logical channels into/from transportblocks (TB) delivered to/from the physical layer on transport channels)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

Physical layers 2 b-20 and 2 b-25 perform an operation of channel-codingand modulating upper layer data, making the upper layer data as an OFDMsymbol and transmitting them to a radio channel, or demodulating andchannel-decoding the OFDM symbol received through the radio channel andtransmitting the demodulated and channel-decoded OFDM symbol to theupper layer.

FIG. 2C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure.

Referring to FIG. 2C, a radio access network of a next generation mobilecommunication system (hereinafter referred to as NR or 5G) is configuredto include a next generation base station (New radio node B, hereinafterNR gNB or NR base station) 2 c-10 and a new radio core network (NR CN) 2c-05. The user terminal (new radio user equipment, hereinafter, NR UE orUE) 2 c-15 accesses the external network through the NR gNB 2 c-10 andthe NR CN 2 c-05.

In FIG. 2C, the NR gNB 2 c-10 corresponds to an evolved node B (eNB) ofthe existing LTE system. The NR gNB is connected to the NR UE 2 c-15 viaa radio channel and may provide a service superior to the existing nodeB. In the next generation mobile communication system, since all usertraffics are served through a shared channel, an apparatus forcollecting state information, such as a buffer state, an availabletransmit power state, and a channel state of the UEs to performscheduling is required. The NR NB 2 c-10 may serve as the device. One NRgNB generally controls a plurality of cells. In order to realizehigh-speed data transmission compared with the current LTE, the NR gNBmay have an existing maximum bandwidth or more, and may be additionallyincorporated into a beam-forming technology may be applied by using OFDMas a radio access technology 2 c-20. Further, an adaptive modulation &coding (hereinafter, called AMC) determining a modulation scheme and achannel coding rate depending on the channel status of the terminal isapplied. The NR CN 1 c-05 may perform functions, such as mobilitysupport, bearer setup, QoS setup, and the like. The NR CN is a devicefor performing a mobility management function for the terminal andvarious control functions and is connected to a plurality of basestations. In addition, the next generation mobile communication systemcan interwork with the existing LTE system, and the NR CN is connectedto the MME 2 c-25 through the network interface. The MME 2 is connectedto the eNB 2 c-30 which is the existing base station.

FIG. 2D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 2D, the radio protocol of the next generation mobilecommunication system is configured to include NR PDCPs 2 d-05 and 2d-40, NR RLCs 2 d-10 and 2 d-35, and NR MACs 2 d-15 and 2 d-30 in theterminal and the NR base station. The main functions of the NR PDCPs 2d-05 and 2 d-40 may include some of the following functions.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Reordering function (PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs)

Retransmission function (Retransmission of PDCP SDUs)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink)

In this case, the reordering function of the NR PDCP apparatus refers toa function of rearranging PDCP PDUs received in a lower layer in orderbased on a PDCP sequence number (SN) and may include a function oftransferring data to an upper layer in the rearranged order, a functionof recording PDCP PDUs lost by the reordering, a function of reporting astate of the lost PDCP PDUs to a transmitting side, and a function ofrequesting a retransmission of the lost PDCP PDUs.

The main functions of the NR RLCs 2 d-10 and 2 d-35 may include some ofthe following functions.

Data transfer function (Transfer of upper layer PDUs)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Out-of-sequence delivery function (Out-of-sequence delivery of upperlayer PDUs)

ARQ function (Error correction through HARQ)

Concatenation, segmentation, reassembly function (Concatenation,segmentation and reassembly of RLC SDUs)

Re-segmentation function (Re-segmentation of RLC data PDUs)

Reordering function (Reordering of RLC data PDUs)

Duplicate detection function (Duplicate detection)

Error detection function (Protocol error detection)

RLC SDU discard function (RLC SDU discard)

RLC re-establishment function (RLC re-establishment)

In this case, the in-sequence delivery function of the NR RLC apparatusrefers to a function of delivering RLC SDUs received from a lower layerto an upper layer in order, and may include a function of reassemblingand transferring an original one RLC SDU which is divided into aplurality of RLC SDUs and received, a function of rearranging thereceived RLC PDUs based on the RLC sequence number (SN) or the PDCPsequence number (SN), a function of recording the RLC PDUs lost by thereordering, a function of reporting a state of the lost RLC PDUs to thetransmitting side, a function of requesting a retransmission of the lostRLC PDUs, a function of transferring only the SLC SDUs before the lostRLC SDU to the upper layer in order when there is the lost RLC SDU, afunction of transferring all the received RLC SDUs to the upper layerbefore a predetermined timer starts if the timer expires even if thereis the lost RLC SDU, or a function of transferring all the RLC SDUsreceived until now to the upper layer in order if the predeterminedtimer expires even if there is the lost RLC SDU. In this case, theout-of-sequence delivery function of the NR RLC apparatus refers to afunction of directly delivering the RLC SDUs received from the lowerlayer to the upper layer regardless of order, and may include a functionof reassembling and transferring an original one RLC SDU which isdivided into several RLC SDUs and received, and a function of storingthe RLC SN or the PDCP SP of the received RLC PDUs and arranging it inorder to record the lost RLC PDUs.

The NR MACs 2 d-15 and 3 d-30 may be connected to several NR RLC layerapparatus configured in one terminal, and the main functions of the NRMAC may include some of the following functions.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing and demultiplexing function (Multiplexing/demultiplexing ofMAC SDUs)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

The NR PHY layers 2 d-20 and 2 d-25 may perform an operation ofchannel-coding and modulating upper layer data, making the upper layerdata as an OFDM symbol and transmitting them to a radio channel, ordemodulating and channel-decoding the OFDM symbol received through theradio channel and transmitting the demodulated and channel-decoded OFDMsymbol to the upper layer.

FIGS. 2EA and 2EB are diagrams illustrating a first MAC PDU structurefor a next generation mobile communication system according to anembodiment of the present disclosure.

Meanwhile, the embodiment of the configuration and transmission of theMAC PDU of the terminal or the base station described below may beinterpreted as an operation between the transmitting end and thereceiving end. In other words, the process of transmitting the uplinkMAC PDU configured by the terminal which is the transmitting end to thebase station which is the receiving end may be applied to the process oftransmitting the downlink MAC PDU configured by the base station whichis the transmitting end to the terminal which is the receiving end.

Referring to FIGS. 2EA and 2EB, if the MAC transmitting side receivesthe RLC PDU (or MAC SDU) from the RLC layer, the MAC transmitting sideinserts an identifier (local channel identity, hereinafter, referred toas LCID) of RLC entity generated by the RLC PDU (or MAC SDU) and a size(length, hereinafter, referred to as an L-field) of the RLC PDU into theMAC header. The LCID and the L-field are inserted one by one per RLCPDU, and therefore if the plurality of RLC PDUs are multiplexed into theMAC PDU, the LCID and the L-field may also be inserted by the number ofRLC PDUs.

Since the information of the MAC header is usually located at the frontpart of the MAC PDU, the LCID and the L-fields are matched with the RLCPDU (or MAC SDU) within the header in order. In other words, MACsub-header 1 indicates information on MAC SDU 1, and MAC sub-header 2indicates information on MAC SDU 2.

For the operation of the physical layer, a total size of the MAC PDU isgiven to the receiving side as separate control information. Since thetotal size of the MAC PDU is a quantized value according to apredetermined criterion, padding may be used in some cases. The paddingmeans certain bits (usually ‘0’) that are filled in the remaining partof the packet so that when the packet is generated with data, the sizeof the packet is byte-aligned.

Since the total size of the MAC PDU is given, an L-field valueindicating the size of the RLC PDU (or MAC SDU) may be unnecessaryinformation in some cases. For example, if only one RLC PDU is stored inthe MAC PDU, the size of the RLC PDU has the possibility that the sizeof the MAC header is equal to a limited value in the size of the MACPDU.

Meanwhile, the VoIP packet consists of an IP/UDP/RTP header and a VoIPframe, and the IP/UDP/RTP header is compressed to about 1 to 15 bytesthrough a header compression protocol called a robust header compression(ROHC) and the size of the VoIP frame always has a constant value withina given codec rate. Therefore, the size of the VoIP packet does notdeviate from a certain range, and it is effective to use a predeterminedvalue rather than informing a value each time like the L-field.

The following Table 2 describes the information that may be included inthe MAC header.

TABLE 2 Variables in MAC Header Variable Usage LCID The LCID mayindicate the identifier of the RLC entity that generates the RLC PDU (orMAC SDU) received from the upper layer. Alternatively, the LCID mayindicate the MAC control element (CE) or the padding. Further, the LCIDmay be defined differently depending on the channel to be transmitted.For example, the LCID may be defined differently according to DL-SCH,UL-SCH, and MCH. L The L may indicate a length of the MAC SDU, and mayindicate a length of the MAC CE having a variable length. In the case ofthe MAC CE having a fixed length, the L-field may be omitted. TheL-field may be omitted for predetermined reasons. The predeterminedreasons are the case where the size of the MAC SDU is fixed, the size ofthe MAC PDU is informed from the transmitting side to the receivingside, or the length may be calculated by calculation at the receivingside. F The F indicates the size of the L-field. If there is no L-field,the F may be omitted, and if there is the F-field, the size of theL-field can be limited to a predetermined size. F2 The F2 indicates thesize of the L-field. If there is no L-field, the F2 may be omitted, andif there is the F2-field, the size of the L-field may be limited to apredetermined size and the L-field may be limited to a size differentfrom the F-field. For example, the F2-field may indicate a larger sizethan the F-field. E E indicates other headers in the MAC heater. Forexample, if the E has a value of 1, variables of another MAC header maybe come. However, if the E has a value of 0, the MAC SDU, the MAC CE, orthe Padding may be come. R Reserved bit.

Referring to FIGS. 2EA and 2EB, 2e-(Format 1-1) may store one MAC SDU orMAC CE. In the above structure, the MAC header is located at a frontpart and the payload is located at a rear part. The header may includethe variables described in Table 2 except for the L-field, andinformation other than the variables described in Table 2.

2e-(Format 1-2a) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC CE, the MAC SDU, andthe padding. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 1e-(Format1-2a). The 2e-(Format 1-2a) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

2e-(Format 1-2b) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC CE, the MAC SDU, andthe padding. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 2e-(Format1-2b). In the 2e-(Format 1-2b) structure, the L-field may be included inall the sub-headers.

2e-(Format 1-2c) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC SDU and the padding.If the MAC CE is generated, the MAC CE may be included in the head ofthe MAC PDU together with the MAC sub-header of the MAC CE. The MACheader consists of several sub-heads. The sub-header may include some ofthe variables described in Table 2, and information other than thevariables described in Table 2. The padding is stored only whennecessary for predetermined reasons. The predetermined reasons refer toa case where it is necessary to set the byte MAC PDU in byte units. Inthis case, each MAC sub-head indicates information corresponding to eachMAC CE, MAC SDU, and padding, in the order numbered on the sub-headersand the payloads of the 2e-(Format 1-2c). The 2e-(Format 1-2c) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU.

2e-(Format 1-2d) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC SDU and the padding.If the MAC CE is generated, the MAC CE may be included in the head ofthe MAC PDU together with the MAC sub-header of the MAC CE. The MACheader consists of several sub-heads. The sub-header may include some ofthe variables described in Table 2, and information other than thevariables described in Table 2. The padding is stored only whennecessary for predetermined reasons. The predetermined reasons refer toa case where it is necessary to set the byte MAC PDU in byte units. Inthis case, each MAC sub-head indicates information corresponding to eachMAC CE, MAC SDU, and padding, in the order numbered on the sub-headersand the payloads of the 2e-(Format 1-2d). In the 2e-(Format 1-2d)structure, the L-field may be included in all the sub-headers.

FIGS. 2FA to 2FF are diagrams illustrating a second MAC PDU structurefor a next generation mobile communication system according to anembodiment of the present disclosure.

Referring to FIGS. 1EA and 1EB, 1e-(Format 2-1) may store one MAC SDU orMAC CE. In the above structure, the payload is located at a front partand the MAC header is located at a rear part. The header may include thevariables described in Table 2 except for the L-field, and informationother than the variables described in Table 2.

2f-(Format 2-2a) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format2-2a). The 2f-(Format 2-2a) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

2f-(Format 2-2a) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format2-2b). The 2f-(Format 2-2b) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

2f-(Format 2-2c) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format2-2b). In the 2e-(Format 2-2d) structure, the L-field may be included inall the sub-headers.

2f-(Format 2-2d) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format2-2d). In the 2f-(Format 2-2d) structure, the L-field may be included inall the sub-headers.

2f-(Format 2-2e) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format2-2e). The 2f-(Format 2-2e) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

2f-(Format 2-2f) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format2-2f). The 2f-(Format 2-2f) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

2f-(Format 2-2g) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format2-2g). In the 2f-(Format 2-2g) structure, the L-field may be included inall the sub-headers.

2f-(Format 2-2h) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format2-2h). In the 2f-(Format 2-2h) structure, the L-field may be included inall the sub-headers.

2f-(Format 2-2i) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 2-2i).The 2f-(Format 2-2j) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

2f-(Format 2-2j) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 2-2i).The 2f-(Format 2-2j) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

2f-(Format 2-2k) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 2-2k). Inthe 2f-(Format 2-2k) structure, the L-field may be included in all thesub-headers.

2f-(Format 2-2l) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 2-2l). Inthe 2f-(Format 2-2l) structure, the L-field may be included in all thesub-headers.

2f-(Format 2-2m) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 2-2m).The 2f-(Format 2-2m) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

2f-(Format 2-2n) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 2-2n).The 2f-(Format 2-2n) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

2f-(Format 2-2o) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 2-2o). Inthe 2f-(Format 2-2o) structure, the L-field may be included in all thesub-headers.

2f-(Format 2-2p) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 2-2p). Inthe 2f-(Format 2-2p) structure, the L-field may be included in all thesub-headers.

2f-(Format 2-2q) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. If the MAC CE is generated, a MAC CE may be located atthe tail part of the MAC PDU together with a sub-header of the MAC CE.The MAC header consists of several sub-heads. The sub-header may includesome of the variables described in Table 2, and information other thanthe variables described in Table 2. The padding is stored only whennecessary for predetermined reasons. The predetermined reasons refer toa case where it is necessary to set the byte MAC PDU in byte units. Inthis case, each MAC sub-head indicates information corresponding to eachMAC SDU, padding, and MAC CE, in the order numbered on the sub-headersand the payloads of the 2f-(Format 2-2q). The 2f-(Format 2-2q) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU.

2f-(Format 2-2r) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. If the MAC CE is generated, together with the sub-headerof the MAC CE, the MAC CE may be located in the middle part of the MACPDU, that is, between the MAC payload and the MAC header, morespecifically, at the head of the MAC sub-headers. The MAC headerconsists of several sub-heads. The sub-header may include some of thevariables described in Table 2, and information other than the variablesdescribed in Table 2. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,padding, and MAC CE, in the order numbered on the sub-headers and thepayloads of the 2f-(Format 2-2r). The 2f-(Format 2-2r) structure ischaracterized in that an L-field is not included in the last sub-header.The receiving side may confirm the L-field value of the remainingsub-headers and subtract the L-field value from the entire length of theMAC PDU to estimate the length of the MAC SDU.

2f-(Format 2-2s) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. If the MAC CE is generated, a MAC CE may be located atthe tail part of the MAC PDU together with a sub-header of the MAC CE.The MAC header consists of several sub-heads. The sub-header may includesome of the variables described in Table 2, and information other thanthe variables described in Table 2. The padding is stored only whennecessary for predetermined reasons. The predetermined reasons refer toa case where it is necessary to set the byte MAC PDU in byte units. Inthis case, each MAC sub-head indicates information corresponding to eachMAC SDU, padding, and MAC CE, in the order numbered on the sub-headersand the payloads of the 2f-(Format 2-2s). In the 2f-(Format 2-2s)structure, the L-field may be included in all the sub-headers.

2f-(Format 2-2t) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. If the MAC CE is generated, together with the sub-headerof the MAC CE, the MAC CE may be located in the middle part of the MACPDU, that is, between the MAC payload and the MAC header, morespecifically, at the head of the MAC sub-headers. The MAC headerconsists of several sub-heads. The sub-header may include some of thevariables described in Table 2, and information other than the variablesdescribed in Table 2. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,padding, and MAC CE, in the order numbered on the sub-headers and thepayloads of the 2f-(Format 2-2t). In the 2f-(Format 2-2t) structure, theL-field may be included in all the sub-headers.

FIGS. 2GA to 2GC are diagrams illustrating a third MAC PDU structure fora next generation mobile communication system according to an embodimentof the present disclosure.

Referring to FIGS. 2GA to 2GC, 2g-(Format 3-1) may store one MAC SDU orMAC CE. In the above structure, the MAC header is located at a frontpart and the payload is located at a rear part. The header may includethe variables described in Table 2 except for the L-field, andinformation other than the variables described in Table 2.

2g-(Format 3-2a) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 2FA to 2FF, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 2g-(Format 3-2a) structure is largelydivided into the MAC CE part and the MAC SDU part. The MAC CEs may belocated at a front part in the order in which they are first generated.In the MAC SDU part, a last segment of one MAC SDU (or RLC PDU or RLCSDU) may be located at a head thereof and a first segment of one MAC SDU(or RLC PDU or RLC SDU) may be located at a tail thereof. The sub-headermay include some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC CE, MAC SDU, and padding, in the ordernumbered on the sub-headers and the payloads of the 2g-(Format 3-2a).For example, the header of the front part becomes the informationindicating the payload of the rear part. The 2g-(Format 3-2a) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The2g-(Format 3-2b) structure is the same as the 2g-(Format 3-2a) structureand may include L-fields in all the sub-headers.

2g-(Format 3-2c) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 2FA to 2FF, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 2g-(Format 3-2c) structure is largelydivided into the MAC CE part and the MAC SDU part. The MAC CEs may belocated at the front part in the order in which they are firstgenerated, and in the MAC SDU part, segments of a MAC SDU (or RLC PDU orRLC SDU) may be located at the tail part of the MAC SDU part. Thesub-header may include some of the variables described in Table 2, andinformation other than the variables described in Table 2. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 2g-(Format3-2c). For example, the header of the front part becomes the informationindicating the payload of the rear part. The 2g-(Format 3-2c) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The2g-(Format 3-2d) structure is the same as the 2g-(Format 3-2c) structureand may include L-fields in all the sub-headers.

2g-(Format 3-2e) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 2FA to 2FF, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 2g-(Format 3-2e) structure is largelydivided into a MAC CE part and a MAC SDU part.

The MAC CEs may be located at a front part of the MAC SDU part in theorder in which they are first generated, and even the MAC CEs may belocated at a rear part of the MAC CE part in the order in which they arefirst generated. In the MAC SDU part, a last segment of one MAC SDU (orRLC PDU or RLC SDU) may be located at a head thereof and a first segmentof one MAC SDU (or RLC PDU or RLC SDU) may be located at a tail thereof.The sub-header may include some of the variables described in Table 2,and information other than the variables described in Table 2. Thepadding is stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 2g-(Format3-2e). For example, the header of the front part becomes the informationindicating the payload of the rear part. The 2g-(Format 3-2e) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The2g-(Format 3-2f) structure is the same as the 2g-(Format 3-2e) structureand may include L-fields in all the sub-headers.

2g-(Format 3-2g) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 2FA to 2FF, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 2g-(Format 3-2g) structure is largelydivided into a MAC CE part and a MAC SDU part. The MAC CEs may belocated at a front part of the MAC SDU part in the order in which theyare first generated, and even the MAC CEs may be located at a rear partof the MAC CE part in the order in which they are first generated. Inthe MAC SDU part, the segments of one MAC SDU (or RLC PDU or RLC SDU)may be located at the tail. The sub-header may include some of thevariables described in Table 2, and information other than the variablesdescribed in Table 2. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,MAC CE, and padding, in the order numbered on the sub-headers and thepayloads of the 2g-(Format 3-2g). For example, the header of the frontpart becomes the information indicating the payload of the rear part.The 2g-(Format 3-2g) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU. The 2g-(Format 3-2h) structure is the same as the2g-(Format 3-2g) structure and may include L-fields in all thesub-headers.

2g-(Format 3-2i) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 2FA to 2FF, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 2g-(Format 3-2i) structure is dividedinto a MAC CE part that may be first generated, a MAC SDU part, and aMAC CE part that are generated later. The MAC CEs may be located at afront part of the MAC SDU part in the order in which they are firstgenerated, and even the MAC CEs may be located at a rear part of the MACCE part in the order in which they are first generated. However, a MACCE (or the MAC CE determined to have the high priority, the MAC CE priorto the MAC SDU, or the MAC CE satisfying the predetermined criterion)that may be generated in advance before being allocated the uplinkresource of the uplink is the MAC CE part that may be generated firstand may be located at the head of the MAC PDU, and the remaining MAC CEsare the MAC CE part that may be generated later and may be located atthe tail of the MAC PDU. In the MAC SDU part, the last segment of oneMAC SDU (or RLC PDU or RLC SDU) may be located at the head of the MACSDU part and the first segment of one MAC SDU (or RLC PDU or RLC SDU)may be located at the tail of the MAC SDU part. The sub-header mayinclude some of the variables described in Table 2, and informationother than the variables described in Table 2. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC CE, MAC SDU, and padding, in the ordernumbered on the sub-headers and the payloads of the 2g-(Format 3-2i).For example, the header of the front part becomes the informationindicating the payload of the rear part. The 2g-(Format 3-2i) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The2g-(Format 3-2j) structure is the same as the 2g-(Format 3-2i) structureand may include L-fields in all the sub-headers.

2g-(Format 3-2k) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 2FA to 2FF, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 2g-(Format 3-2k) structure is dividedinto a MAC CE part that may be first generated, a MAC SDU part, and aMAC CE part that are generated later. The MAC CEs may be located at afront part of the MAC SDU part in the order in which they are firstgenerated, and even the MAC CEs may be located at a rear part of the MACCE part in the order in which they are first generated. However, a MACCE (or the MAC CE determined to have the high priority, the MAC CE priorto the MAC SDU, or the MAC CE satisfying the predetermined criterion)that may be generated in advance before being allocated the uplinkresource of the uplink is the MAC CE part that may be generated firstand may be located at the head of the MAC PDU, and the remaining MAC CEsare the MAC CE part that may be generated later and may be located atthe tail of the MAC PDU. In the MAC SDU part, the segments of one MACSDU (or RLC PDU or RLC SDU) may be located at the tail of the MAC SDUpart. The sub-header may include some of the variables described inTable 2, and information other than the variables described in Table 2.The padding is stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 2g-(Format3-2k). For example, the header of the front part becomes the informationindicating the payload of the rear part. The 2g-(Format 3-2k) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The2g-(Format 3-2l) structure is the same as the 2g-(Format 3-2k) structureand may include L-fields in all the sub-headers.

FIG. 2H is a diagram illustrating MAC SDU (or RLC PDU) structures for anext generation mobile communication system according to an embodimentof the present disclosure.

Referring to FIG. 2H, in the 2h-(Format 4-1) structure of FIG. 2H, theRLC SN allocated in the RLC layer may be included in the RLC header.However, if the PDCP SP is shared, the RLC SN is not allocated in theRLC layer and thus the RLC SN may not exist in the RLC header. The RLCheader may not have a placement indicator (PI) field. The PI field is afield indicating a location of the following LI field. The LI field is afield indicating a size of the immediately following RLC SDU (or PDCPPDU), and may be added in the RLC layer. The 2h-(Format 4-1) structureis a structure in which one LI field and one RLC SDU may beconsecutively arranged in a pair, and the segment may also be arrangedalone and a header is disposed in the front. The last segment of one RLCSDU (or PDCP PDU) may be at the head of the RLC payload portion, and thefirst segment of the RLC SDU (or PDCP PDU) may be at the tail of the RLCpayload portion.

In the 2h-(Format 4-2) structure of FIG. 2H, the RLC SN allocated in theRLC layer may be included in the RLC header. However, if the PDCP SP isshared, the RLC SN is not allocated in the RLC layer and thus the RLC SNmay not exist in the RLC header. The RLC header may not have theplacement indicator (PI) field. The PI field is a field indicating theposition of the LI field at the front part and may be added in the RLClayer. The LI field is a field indicating a size of the immediatelypreceding RLC SDU (or PDCP PDU). The 2h-(Format 4-2) structure is astructure in which one RLC field and one LI field may be consecutivelyarranged in a pair, and the segment may also be arranged alone and aheader is disposed at the rear part. The last segment of one RLC SDU (orPDCP PDU) may be at the head of the RLC payload portion, and the firstsegment of the RLC SDU (or PDCP PDU) may be at the tail of the RLCpayload portion.

In the 2h-(Format 4-3) structure of FIG. 2H, the RLC SN allocated in theRLC layer may be included in the RLC header. However, if the PDCP SP isshared, the RLC SN is not allocated in the RLC layer and thus the RLC SNmay not exist in the RLC header. The RLC header may not have theplacement indicator (PI) field. The PI field is a field indicating alocation of the following LI field. The LI field is a field indicating asize of the immediately following RLC SDU (or PDCP PDU), and may beadded to the PDCP header in the RLC layer. The 2h-(Format 4-3) structureis a structure in which one LI field and one RLC SDU may beconsecutively arranged in a pair, and the segment may also be arrangedalone and a header is disposed in the front. The last segment of one RLCSDU (or PDCP PDU) may be at the head of the RLC payload portion, and thefirst segment of the RLC SDU (or PDCP PDU) may be at the tail of the RLCpayload portion.

In the 2h-(Format 4-4) structure of FIG. 2H, the RLC SN allocated in theRLC layer may be included in the RLC header. However, if the PDCP SP isshared, the RLC SN is not allocated in the RLC layer and thus the RLC SNmay not exist in the RLC header. The RLC header may not have theplacement indicator (PI) field. The PI field is a field indicating theposition of the LI field at the front part and may be added to the PDCPheader in the PDCP layer. The LI field is a field indicating a size ofthe immediately preceding RLC SDU (or PDCP PDU). The 2h-(Format 4-4)structure is a structure in which one RLC field and one LI field may beconsecutively arranged in a pair, and the segment may also be arrangedalone and a header is disposed at the rear part. The last segment of oneRLC SDU (or PDCP PDU) may be at the head of the RLC payload portion, andthe first segment of the RLC SDU (or PDCP PDU) may be at the tail of theRLC payload portion.

In the 2h-(Format 4-5) structure of FIG. 2H, the RLC SN allocated in theRLC layer may be included in the RLC header. However, if the PDCP SP isshared, the RLC SN is not allocated in the RLC layer and thus the RLC SNmay not exist in the RLC header. The RLC header may have the lengthindicator (LI) field and an E field. The LI field is a field indicatingthe size of the immediately following RLC SDU (PDCP PDU), and the Efield indicates whether another LI or E field follows the immediatelyfollowing RLC SDU. The 2h-(Format 4-5) structure is a structure in whichone RLC field, one LI field, and one E field may be consecutivelyarranged in a pair and the segment may also be arranged alone and theheader is disposed in the front. The last segment of one RLC SDU (orPDCP PDU) may be at the head of the RLC payload portion, and the firstsegment of the RLC SDU (or PDCP PDU) may be at the tail of the RLCpayload portion.

In the 2h-(Format 4-6) structure of FIG. 2H, the RLC SN allocated in theRLC layer may be included in the RLC header. However, if the PDCP SP isshared, the RLC SN is not allocated in the RLC layer and thus the RLC SNmay not exist in the RLC header. The RLC header may have or may not havean LI field. The LI field is a field indicating a size of theimmediately following RLC SDU (or PDCP PDU). In the 2h-(Format 4-6)structure, one RLC SDU (or one PDCP PDU) is included in one RLC PDU, andcorresponds to the case where the concatenation is not performed in theRLC layer. In addition, it is also a structure in which the header isdisposed at the front part.

In the 2h-(Format 4-7) structure of FIG. 2H, the RLC SN allocated in theRLC layer may be included in the RLC header. However, if the PDCP SP isshared, the RLC SN is not allocated in the RLC layer and thus the RLC SNmay not exist in the RLC header. The RLC header may have or may not havethe LI field. The LI field is a field indicating a size of theimmediately following RLC SDU (or PDCP PDU). In the 2h-(Format 4-6)structure, one RLC SDU (or one PDCP PDU) is included in one RLC PDU, andcorresponds to the case where the concatenation is not performed in theRLC layer. In addition, it is also a structure in which the header isdisposed at the rear part.

FIG. 2I is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure.

Referring to FIG. 2I, the terminal includes a radio frequency (RF)processor 2 i-10, a baseband processor 2 i-20, a storage 2 i-30, and acontroller 2 i-40.

The RF processor 2 i-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 2 i-10 up-converts a baseband signalprovided from the baseband processor 2 i-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 2 i-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, adigital to analog converter (DAC), an analog to digital converter (ADC),or the like. FIG. 2I illustrates only one antenna but the terminal mayinclude a plurality of antennas. Further, the RF processor 2 i-10 mayinclude a plurality of RF chains. Further, the RF processor 2 i-10 mayperform beamforming. For the beamforming, the RF processor 2 i-10 mayadjust a phase and a size of each of the signals transmitted andreceived through a plurality of antennas or antenna elements. Inaddition, the RF processor may perform MIMO and may receive a pluralityof layers when performing the MIMO operation. The RF processor 2 i-10may perform reception beam sweeping by appropriately configuring aplurality of antennas or antenna elements under the control of thecontroller or adjust a direction and a beam width of the reception beamso that the reception beam is resonated with the transmission beam.

The baseband processor 2 i-20 performs a conversion function between abaseband signal and a bit string according to a physical layer standardof a system. For example, when data are transmitted, the basebandprocessor 2 i-20 generates complex symbols by coding and modulating atransmitted bit string. Further, when data are received, the basebandprocessor 2 i-20 recovers the received bit string by demodulating anddecoding the baseband signal provided from the RF processor 2 i-10. Forexample, according to the OFDM scheme, when data are transmitted, thebaseband processor 2 i-20 generates the complex symbols by coding andmodulating the transmitting bit string, maps the complex symbols tosub-carriers, and then performs an inverse fast Fourier transform (IFFT)operation and a cyclic prefix (CP) insertion to construct the OFDMsymbols. Further, when data are received, the baseband processor 2 i-20divides the baseband signal provided from the RF processor 2 i-10 in anOFDM symbol unit and recovers the signals mapped to the sub-carriers bya fast Fourier transform (FFT) operation and then recovers the receivedbit string by the modulation and decoding.

The baseband processor 2 i-20 and the RF processor 2 i-10 transmit andreceive a signal as described above. Therefore, the baseband processor 2i-20 and the RF processor 2 i-10 may be called a transmitter, areceiver, a transceiver, or a communication unit. Further, at least oneof the baseband processor 2 i-20 and the RF processor 2 i-10 may includea plurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 2 i-20 and the RF processor 2 i-10 may include differentcommunication modules to process signals in different frequency bands.For example, the different wireless access technologies may include anLTE network, an NR network, and the like. Further, different frequencybands may include a super high frequency (SHF) (for example: 2.5 GHz, 5GHz) band, a millimeter wave (for example: 60 GHz) band.

The storage 2 i-30 stores data, such as basic programs, applicationprograms, and configuration information for the operation of theterminal. The storage 2 i-30 provides the stored data according to therequest of the controller 2 i-40.

The controller 2 i-40 includes a multiple connection processor 2 i-42and controls the overall operations of the terminal. For example, thecontroller 2 i-40 transmits and receives a signal through the basebandprocessor 2 i-20 and the RF processor 2 i-10. Further, the controller 2i-40 records and reads data in and from the storage 2 i-40. For thispurpose, the controller 2 i-40 may include at least one processor. Forexample, the controller 2 i-40 may include a communication processor(CP) performing a control for communication and an application processor(AP) controlling an upper layer, such as the application programs.

FIG. 2J is a block configuration diagram of TRP in a wirelesscommunication system according to an embodiment of the presentdisclosure.

Referring to FIG. 2J, the base station is configured to include an RFprocessor 2 j-10, a baseband processor 2 j-20, a communication unit 2j-30, a storage 2 j-40, and a controller 2 j-50.

The RF processor 2 j-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 2 j-10 up-converts a baseband signalprovided from the baseband processor 2 j-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 2 j-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC,an ADC, or the like. FIG. 2J illustrates only one antenna but the firstaccess node may include a plurality of antennas. Further, the RFprocessor 2 j-10 may include a plurality of RF chains. Further, the RFprocessor 2 j-10 may perform the beamforming. For the beamforming, theRF processor 2 j-10 may adjust a phase and a size of each of the signalstransmitted/received through a plurality of antennas or antennaelements. The RF processor may perform a downward MIMO operation bytransmitting one or more layers.

The baseband processor 2 j-20 performs a conversion function between thebaseband signal and the bit string according to the physical layerstandard of the first radio access technology. For example, when dataare transmitted, the baseband processor 2 j-20 generates complex symbolsby coding and modulating a transmitted bit string. Further, when dataare received, the baseband processor 2 j-20 recovers the received bitstring by demodulating and decoding the baseband signal provided fromthe RF processor 2 j-10. For example, according to the OFDM scheme, whendata are transmitted, the baseband processor 2 j-20 generates thecomplex symbols by coding and modulating the transmitting bit string,maps the complex symbols to the sub-carriers, and then performs the IFFToperation and the CP insertion to construct the OFDM symbols. Further,when data are received, the baseband processor 2 j-20 divides thebaseband signal provided from the RF processor 2 j-10 in the OFDM symbolunit and recovers the signals mapped to the sub-carriers by the FFToperation and then recovers the receiving bit string by the modulationand decoding. The baseband processor 1 j-20 and the RF processor 1 j-10transmit and receive a signal as described above. Therefore, thebaseband processor 2 j-20 and the RF processor 2 j-10 may be called atransmitter, a receiver, a transceiver, or a communication unit.

The communication unit 2 j-30 provides an interface for performingcommunication with other nodes within the network.

The storage 2 j-40 stores data, such as basic programs, applicationprograms, and configuration information for the operation of the mainbase station. More particularly, the storage 2 j-40 may store theinformation on the bearer allocated to the accessed terminal, themeasured results reported from the accessed terminal, and the like.Further, the storage 2 j-40 may store information that is adetermination criterion on whether to provide a multiple connection tothe terminal or stop the multiple connection to the terminal. Further,the storage 2 j-40 provides the stored data according to the request ofthe controller 2 j-50.

The controller 2 j-50 includes a multiple connection processor 2 j-52and controls the general operations of the main base station. Forexample, the controller 2 j-50 transmits/receives a signal through thebaseband processor 2 j-20 and the RF processor 2 j-10 or thecommunication unit 2 j-30. Further, the controller 2 j-50 records andreads data in and from the storage 2 j-40. For this purpose, thecontroller 2 j-50 may include at least one processor.

Third Embodiment

FIG. 3A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure.

Referring to FIG. 3A, a radio access network of an LTE system isconfigured to include next generation base stations (evolved node B,hereinafter, eNB, Node B, or base station) 3 a-05, 3 a-10, 3 a-15, and 3a-20, a mobility management entity (MME) 3 a-25, and a serving-gateway(S-GW) 3 a-30. User equipment (hereinafter, UE or terminal) 3 a-35accesses an external network through the eNBs 3 a-05 to 3 a-20 and theS-GW 3 a-30.

In FIG. 3A, the eNB 3 a-05 to 3 a-20 correspond to the existing node Bof the UMTS system. The eNB is connected to the UE 3 a-35 through aradio channel and performs more complicated role than the existing nodeB. In the LTE system, in addition to a real-time service like a voiceover Internet protocol (VoIP) through the Internet protocol, all theuser traffics are served through a shared channel and therefore anapparatus for collecting and scheduling status information, such as abuffer status, an available transmit power status, and a channel stateof the terminals is required. Here, the eNBs 3 a-05 to 3 a-20 takecharge of the collecting and scheduling. One eNB generally controls aplurality of cells. For example, to implement a transmission rate of 100Mbps, the LTE system uses, as a radio access technology, OFDM in, forexample, a bandwidth of 20 MHz. Further, an adaptive modulation & coding(hereinafter, referred to as AMC) determining a modulation scheme and achannel coding rate according to a channel status of the terminal isapplied. The S-GW 3 a-30 is an apparatus for providing a data bearer andgenerates or removes the data bearer according to the control of the MME3 a-25. The MME is an apparatus for performing a mobility managementfunction for the terminal and various control functions and is connectedto a plurality of base stations.

FIG. 3B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure.

Referring to FIG. 3B, the radio protocol of the LTE system is configuredto include PDCPs 3 b-05 and 3 b-40, RLCs 3 b-10 and 3 b-35, and mediumaccess controls (MMCs) 3 b-15 and 3 b-30 in the terminal and the eNB,respectively. The PDCPs 3 b-05 and 3 b-40 are in charge of operations,such as IP header compression/decompression. The main functions of thePDCP are summarized as follows.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUsat PDCP re-establishment procedure for RLC AM)

Reordering function (For split bearers in DC (only support for RLC AM):PDCP PDU routing for transmission and PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs atPDCP re-establishment procedure for RLC AM)

Retransmission function (Retransmission of PDCP SDUs at handover and,for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure,for RLC AM)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink.)

The RLCs 3 b-10 and 3 b-35 reconfigures the PDCP PDU to an appropriatesize to perform the ARQ operation or the like. The main functions of theRLC are summarized as follows.

Data transfer function (Transfer of upper layer PDUs)

ARQ function (Error Correction through ARQ (only for AM data transfer))

Concatenation, segmentation, reassembly functions (Concatenation,segmentation and reassembly of RLC SDUs (only for UM and AM datatransfer))

Re-segmentation function (Re-segmentation of RLC data PDUs (only for AMdata transfer))

Reordering function (Reordering of RLC data PDUs (only for UM and AMdata transfer)

Duplicate detection function (Duplicate detection (only for UM and AMdata transfer))

Error detection function (Protocol error detection (only for AM datatransfer))

RLC SDU discard function (RLC SDU discard (only for UM and AM datatransfer))

RLC re-establishment function (RLC re-establishment)

The MACs 3 b-15 and 3 b-30 are connected to several RLC layer apparatusconfigured in one terminal and perform an operation of multiplexing RLCPDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU.The main functions of the MAC are summarized as follows.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MACSDUs belonging to one or different logical channels into/from transportblocks (TB) delivered to/from the physical layer on transport channels)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

Physical layers 3 b-20 and 3 b-25 perform an operation of channel-codingand modulating higher layer data, making the upper layer data as an OFDMsymbol and transmitting them to a radio channel, or demodulating andchannel-decoding the OFDM symbol received through the radio channel andtransmitting the demodulated and channel-decoded OFDM symbol to theupper layer.

FIG. 3C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure.

Referring to FIG. 3C, a radio access network of a next generation mobilecommunication system (hereinafter referred to as NR or 5G) is configuredto include a next generation base station (New radio node B, hereinafterNR gNB or NR base station) 3 c-10 and a new radio core network (NR CN) 3c-05. The user terminal (new radio user equipment, hereinafter, NR UE orUE) 3 c-15 accesses the external network through the NR gNB 3 c-10 andthe NR CN 3 c-05.

In FIG. 3C, the NR gNB 3 c-10 corresponds to an evolved node B (eNB) ofthe existing LTE system. The NR gNB is connected to the NR UE 3 c-15 viaa radio channel and may provide a service superior to the existing nodeB. In the next generation mobile communication system, since all usertraffics are served through a shared channel, an apparatus forcollecting state information, such as a buffer state, an availabletransmit power state, and a channel state of the UEs to performscheduling is required. The NR NB 3 c-10 may serve as the device. One NRgNB generally controls a plurality of cells. In order to realizehigh-speed data transmission compared with the current LTE, the NR gNBmay have an existing maximum bandwidth or more, and may be additionallyincorporated into a beam-forming technology may be applied by using OFDMas a radio access technology 3 c-20. Further, an adaptive modulation &coding (hereinafter, called AMC) determining a modulation scheme and achannel coding rate depending on a channel status of the terminal isapplied. The NR CN 3 c-05 05 may perform functions, such as mobilitysupport, bearer setup, QoS setup, and the like. The NR CN is a devicefor performing a mobility management function for the terminal andvarious control functions and is connected to a plurality of basestations. In addition, the next generation mobile communication systemcan interwork with the existing LTE system, and the NR CN is connectedto the MME 3 c-25 through the network interface. The MME is connected tothe eNB 3 c-30 which is the existing base station.

FIG. 3D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 3D, the radio protocol of the next generation mobilecommunication system is configured to include NR PDCPs 3 d-05 and 3d-40, NR RLCs 3 d-10 and 3 d-35, and NR MACs 3 d-15 and 3 d-30 in theterminal and the NR base station. The main functions of the NR PDCPs 3d-05 and 3 d-40 may include some of the following functions.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Reordering function (PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs)

Retransmission function (Retransmission of PDCP SDUs)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink)

In this case, the reordering function of the NR PDCP apparatus refers toa function of rearranging PDCP PDUs received in a lower layer in orderbased on a PDCP sequence number (SN) and may include a function oftransferring data to an upper layer in the rearranged order, a functionof recording PDCP PDUs lost by the reordering, a function of reporting astate of the lost PDCP PDUs to a transmitting side, and a function ofrequesting a retransmission of the lost PDCP PDUs.

The main functions of the NR RLCs 3 d-10 and 3 d-35 may include some ofthe following functions.

Data transfer function (Transfer of upper layer PDUs)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Out-of-sequence delivery function (Out-of-sequence delivery of upperlayer PDUs)

ARQ function (Error correction through HARQ)

Concatenation, segmentation, reassembly function (Concatenation,segmentation and reassembly of RLC SDUs)

Re-segmentation function (Re-segmentation of RLC data PDUs)

Reordering function (Reordering of RLC data PDUs)

Duplicate detection function (Duplicate detection)

Error detection function (Protocol error detection)

RLC SDU discard function (RLC SDU discard)

RLC re-establishment function (RLC re-establishment)

In this case, the in-sequence delivery function of the NR RLC apparatusrefers to a function of delivering RLC SDUs received from a lower layerto an upper layer in order, and may include a function of reassemblingand transferring an original one RLC SDU which is divided into aplurality of RLC SDUs and received, a function of rearranging thereceived RLC PDUs based on the RLC sequence number (SN) or the PDCPsequence number (SN), a function of recording the RLC PDUs lost by thereordering, a function of reporting a state of the lost RLC PDUs to thetransmitting side, a function of requesting a retransmission of the lostRLC PDUs, a function of transferring only the SLC SDUs before the lostRLC SDU to the upper layer in order when there is the lost RLC SDU, afunction of transferring all the received RLC SDUs to the upper layerbefore a predetermined timer starts if the timer expires even if thereis the lost RLC SDU, or a function of transferring all the RLC SDUsreceived until now to the upper layer in order if the predeterminedtimer expires even if there is the lost RLC SDU. In this case, theout-of-sequence delivery function of the NR RLC apparatus refers to afunction of directly delivering the RLC SDUs received from the lowerlayer to the upper layer regardless of order, and may include a functionof reassembling and transferring an original one RLC SDU which isdivided into several RLC SDUs and received, and a function of storingthe RLC SN or the PDCP SP of the received RLC PDUs and arranging it inorder to record the lost RLC PDUs.

The NR MACs 3 d-15 and 3 d-30 may be connected to several NR RLC layerapparatus configured in one terminal, and the main functions of the NRMAC may include some of the following functions.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing and demultiplexing function (Multiplexing/demultiplexing ofMAC SDUs)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

The NR PHY layers 3 d-20 and 3 d-25 may perform an operation ofchannel-coding and modulating higher layer data, making the upper layerdata as an OFDM symbol and transmitting them to a radio channel, ordemodulating and channel-decoding the OFDM symbol received through theradio channel and transmitting the demodulated and channel-decoded OFDMsymbol to the upper layer.

FIGS. 3EA and 3EB are diagrams illustrating a first MAC PDU structurefor a next generation mobile communication system according to anembodiment of the present disclosure.

Meanwhile, the embodiment of the configuration and transmission of theMAC PDU of the terminal or the base station described below may beinterpreted as an operation between the transmitting end and thereceiving end. In other words, the process of transmitting the uplinkMAC PDU configured by the terminal which is the transmitting end to thebase station which is the receiving end may be applied to the process oftransmitting the downlink MAC PDU configured by the base station whichis the transmitting end to the terminal which is the receiving end.

Referring to FIGS. 3EA and 3EB, if the MAC transmitting side receivesthe RLC PDU (or MAC SDU) from the RLC layer, the MAC transmitting sideinserts an identifier (local channel identity, hereinafter, referred toas LCID) of RLC entity generated by the RLC PDU (or MAC SDU) and a size(length, hereinafter, referred to as an L-field) of the RLC PDU into theMAC header. The LCID and the L-field are inserted one by one per RLCPDU, and therefore if the plurality of RLC PDUs are multiplexed into theMAC PDU, the LCID and the L-field may also be inserted by the number ofRLC PDUs.

Since the information of the MAC header is usually located at the frontpart of the MAC PDU, the LCID and the L-fields are matched with the RLCPDU (or MAC SDU) within the header in order. In other words, MACsub-header 1 indicates information on MAC SDU 1, and MAC sub-header 2indicates information on MAC SDU 2.

For the operation of the physical layer, a total size of the MAC PDU isgiven to the receiving side as separate control information. Since thetotal size of the MAC PDU is a quantized value according to apredetermined criterion, padding may be used in some cases. The paddingmeans certain bits (usually ‘0’) that are filled in the remaining partof the packet so that when the packet is generated with data, the sizeof the packet is byte-aligned.

Since the total size of the MAC PDU is given, an L-field valueindicating the size of the RLC PDU (or MAC SDU) may be unnecessaryinformation in some cases. For example, if only one RLC PDU is stored inthe MAC PDU, the size of the RLC PDU has the possibility that the sizeof the MAC header is equal to a limited value in the size of the MACPDU.

Meanwhile, the VoIP packet consists of an IP/UDP/RTP header and a VoIPframe, and the IP/UDP/RTP header is compressed to about 1 to 15 bytesthrough a header compression protocol called a robust header compression(ROHC) and the size of the VoIP frame always has a constant value withina given code rate. Therefore, the size of the VoIP packet does notdeviate from a certain range, and it is effective to use a predeterminedvalue rather than informing a value each time like the L-field.

The following Table 3 describes the information that may be included inthe MAC header.

TABLE 3 Variables in MAC Header Variable Usage LCID The LCID mayindicate the identifier of the RLC entity that generates the RLC PDU (orMAC SDU) received from the upper layer. Alternatively, the LCID mayindicate the MAC control element (CE) or the padding. Further, the LCIDmay be defined differently depending on the channel to be transmitted.For example, the LCID may be defined differently according to DL-SCH,UL-SCH, and MCH. L The L may indicate a length of the MAC SDU, and mayindicate a length of the MAC CE having a variable length. In the case ofthe MAC CE having a fixed length, the L-field may be omitted. TheL-field may be omitted for predetermined reasons. The predeterminedreasons are the case where the size of the MAC SDU is fixed, the size ofthe MAC PDU is informed from the transmitting side to the receivingside, or the length may be calculated by calculation at the receivingside. F The F indicates the size of the L-field. If there is no L-field,the F may be omitted, and if there is the F-field, the size of theL-field can be limited to a predetermined size. F2 The F2 indicates thesize of the L-field. If there is no L-field, the F2 may be omitted, andif there is the F2-field, the size of the L-field may be limited to apredetermined size and the L-field may be limited to a size differentfrom the F-field. For example, the F2-field may indicate a larger sizethan the F-field. E E indicates other headers in the MAC heater. Forexample, if the E has a value of 1, variables of another MAC header maybe come. However, if the E has a value of 0, the MAC SDU, the MAC CE, orthe Padding may be come. R Reserved bit.

Referring to FIGS. 3EA and 3EB, 3e-(Format 1-1) may store one MAC SDU orMAC CE. In the above structure, the MAC header is located at a frontpart and the payload is located at a rear part. The header may includethe variables described in Table 3 except for the L-field, andinformation other than the variables described in Table 3.

3e-(Format 1-2a) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC CE, the MAC SDU, andthe padding. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 3e-(Format1-2a). The 3e-(Format 1-2a) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

3e-(Format 1-2b) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC CE, the MAC SDU, andthe padding. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 3e-(Format1-2b). In the 3e-(Format 1-2b) structure, the L-field may be included inall the sub-headers.

3e-(Format 1-2c) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC SDU and the padding.If the MAC CE is generated, the MAC CE may be included in the head ofthe MAC PDU together with the MAC sub-header of the MAC CE. The MACheader consists of several sub-heads. The sub-header may include some ofthe variables described in Table 3, and information other than thevariables described in Table 3. The padding is stored only whennecessary for predetermined reasons. The predetermined reasons refer toa case where it is necessary to set the byte MAC PDU in byte units. Inthis case, each MAC sub-head indicates information corresponding to eachMAC CE, MAC SDU, and padding, in the order numbered on the sub-headersand the payloads of the 3e-(Format 1-2c). The 3e-(Format 1-2c) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU.

3e-(Format 1-2d) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC SDU and the padding.If the MAC CE is generated, the MAC CE may be included in the head ofthe MAC PDU together with the MAC sub-header of the MAC CE. The MACheader consists of several sub-heads. The sub-header may include some ofthe variables described in Table 3, and information other than thevariables described in Table 3. The padding is stored only whennecessary for predetermined reasons. The predetermined reasons refer toa case where it is necessary to set the byte MAC PDU in byte units. Inthis case, each MAC sub-head indicates information corresponding to eachMAC CE, MAC SDU, and padding, in the order numbered on the sub-headersand the payloads of the 3e-(Format 1-2d). In the 3e-(Format 1-2d)structure, the L-field may be included in all the sub-headers.

FIGS. 3FA to 3FE are diagrams illustrating a second MAC PDU structurefor a next generation mobile communication system according to anembodiment of the present disclosure.

Referring to FIGS. 3FA to 3FE, 3f-(Format 2-1) may store one MAC SDU orMAC CE. In the above structure, the payload is located at a front partand the MAC header is located at a rear part. The header may include thevariables described in Table 3 except for the L-field, and informationother than the variables described in Table 3.

3f-(Format 2-1) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 3f-(Format2-2a). The 3f-(Format 2-2a) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

3f-(Format 2-2b) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 3f-(Format2-2b). The 3f-(Format 2-2b) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

3f-(Format 2-2c) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 3f-(Format2-2c). In the 3f-(Format 2-2c) structure, the L-field may be included inall the sub-headers.

3f-(Format 2-2d) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 3f-(Format2-2d). In the 3f-(Format 2-2d) structure, the L-field may be included inall the sub-headers.

3f-(Format 2-2e) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 3f-(Format2-2e). The 3f-(Format 2-2e) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

3f-(Format 2-2f) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 3f-(Format2-2f). The 3f-(Format 2-2f) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

3f-(Format 2-2g) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 3f-(Format2-2g). In the 3f-(Format 2-2g) structure, the L-field may be included inall the sub-headers.

3f-(Format 2-2h) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 3f-(Format2-2h). In the 3f-(Format 2-2h) structure, the L-field may be included inall the sub-headers.

3f-(Format 2-2i) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 3f-(Format 2-2i).The 3f-(Format 2-2i) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

3f-(Format 2-2j) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 3f-(Format 2-2j).The 3f-(Format 2-2j) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

3f-(Format 2-2k) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 3f-(Format 2-2k). Inthe 3f-(Format 2-2k) structure, the L-field may be included in all thesub-headers.

3f-(Format 2-2l) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 3f-(Format 2-2l). Inthe 3f-(Format 2-2l) structure, the L-field may be included in all thesub-headers.

3f-(Format 2-2m) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 3f-(Format 2-2m).The 3f-(Format 2-2m) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

3f-(Format 2-2n) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 3f-(Format 2-2n).The 3f-(Format 2-2n) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

3f-(Format 2-2o) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 3f-(Format 2-2o). Inthe 3f-(Format 2-2o) structure, the L-field may be included in all thesub-headers.

3f-(Format 2-2p) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 3f-(Format 2-2p). Inthe 3f-(Format 2-2p) structure, the L-field may be included in all thesub-headers.

3f-(Format 2-2q) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. If the MAC CE is generated, a MAC CE may be located atthe tail part of the MAC PDU together with a sub-header of the MAC CE.The MAC header consists of several sub-heads. The sub-header may includesome of the variables described in Table 3, and information other thanthe variables described in Table 3. The padding is stored only whennecessary for predetermined reasons. The predetermined reasons refer toa case where it is necessary to set the byte MAC PDU in byte units. Inthis case, each MAC sub-head indicates information corresponding to eachMAC SDU, padding, and MAC CE, in the order numbered on the sub-headersand the payloads of the 3f-(Format 2-2q). The 3f-(Format 2-2q) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU.

3f-(Format 2-2r) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. If the MAC CE is generated, together with the sub-headerof the MAC CE, the MAC CE may be located in the middle part of the MACPDU, that is, between the MAC payload and the MAC header, morespecifically, at the head of the MAC sub-headers. The MAC headerconsists of several sub-heads. The sub-header may include some of thevariables described in Table 3, and information other than the variablesdescribed in Table 3. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,padding, and MAC CE, in the order numbered on the sub-headers and thepayloads of the 3f-(Format 2-2r). The 3f-(Format 2-2r) structure ischaracterized in that an L-field is not included in the last sub-header.The receiving side may confirm the L-field value of the remainingsub-headers and subtract the L-field value from the entire length of theMAC PDU to estimate the length of the MAC SDU.

3f-(Format 2-2s) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. If the MAC CE is generated, a MAC CE may be located atthe tail part of the MAC PDU together with a sub-header of the MAC CE.The MAC header consists of several sub-heads. The sub-header may includesome of the variables described in Table 3, and information other thanthe variables described in Table 3. The padding is stored only whennecessary for predetermined reasons. The predetermined reasons refer toa case where it is necessary to set the byte MAC PDU in byte units. Inthis case, each MAC sub-head indicates information corresponding to eachMAC SDU, padding, and MAC CE, in the order numbered on the sub-headersand the payloads of the 3f-(Format 2-2s). In the 3f-(Format 2-2s)structure, the L-field may be included in all the sub-headers.

3f-(Format 2-2t) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. If the MAC CE is generated, together with the sub-headerof the MAC CE, the MAC CE may be located in the middle part of the MACPDU, that is, between the MAC payload and the MAC header, morespecifically, at the head of the MAC sub-headers. The MAC headerconsists of several sub-heads. The sub-header may include some of thevariables described in Table 3, and information other than the variablesdescribed in Table 3. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,padding, and MAC CE, in the order numbered on the sub-headers and thepayloads of the 3f-(Format 2-2t). In the 3f-(Format 2-2t) structure, theL-field may be included in all the sub-headers.

FIGS. 3GA to 3GC are diagrams illustrating a third MAC PDU structure fora next generation mobile communication system according to an embodimentof the present disclosure.

Referring to FIG. 3GA to 3GC, 3g-(Format 3-1) may store one MAC SDU orMAC CE. In the above structure, the MAC header is located at a frontpart and the payload is located at a rear part. The header may includethe variables described in Table 3 except for the L-field, andinformation other than the variables described in Table 3.

3g-(Format 3-2a) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 3FA to 3FEB, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 3g-(Format 3-2a) structure is largelydivided into the MAC CE part and the MAC SDU part. The MAC CEs may belocated at a front part in the order in which they are first generated.In the MAC SDU part, a last segment of one MAC SDU (or RLC PDU or RLCSDU) may be located at a head thereof and a first segment of one MAC SDU(or RLC PDU or RLC SDU) may be located at a tail thereof. The sub-headermay include some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC CE, MAC SDU, and padding, in the ordernumbered on the sub-headers and the payloads of the 3g-(Format 3-2a).For example, the header of the front part becomes the informationindicating the payload of the rear part. The 3g-(Format 3-2a) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The3g-(Format 3-2b) structure is the same as the 3g-(Format 3-2a) structureand may include L-fields in all the sub-headers.

3g-(Format 3-2c) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 3FA to 3FEB, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 3g-(Format 3-2c) structure is largelydivided into the MAC CE part and the MAC SDU part. The MAC CEs may belocated at the front part in the order in which they are firstgenerated, and in the MAC SDU part, segments of a MAC SDU (or RLC PDU orRLC SDU) may be located at the tail part of the MAC SDU part. Thesub-header may include some of the variables described in Table 3, andinformation other than the variables described in Table 3. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 3g-(Format3-2c). For example, the header of the front part becomes the informationindicating the payload of the rear part. The 3g-(Format 3-2c) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The3g-(Format 3-2d) structure is the same as the 3g-(Format 3-2c) structureand may include L-fields in all the sub-headers.

3g-(Format 3-2e) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 3FA to 3FEB, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 3g-(Format 3-2e) structure is largelydivided into a MAC CE part and a MAC SDU part. The MAC CEs may belocated at a front part of the MAC SDU part in the order in which theyare first generated, and even the MAC CEs may be located at a rear partof the MAC CE part in the order in which they are first generated. Inthe MAC SDU part, a last segment of one MAC SDU (or RLC PDU or RLC SDU)may be located at a head thereof and a first segment of one MAC SDU (orRLC PDU or RLC SDU) may be located at a tail thereof. The sub-header mayinclude some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, MAC CE, and padding, in the ordernumbered on the sub-headers and the payloads of the 3g-(Format 3-2e).For example, the header of the front part becomes the informationindicating the payload of the rear part. The 3g-(Format 3-2e) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The3g-(Format 3-2f) structure is the same as the 3g-(Format 3-2e) structureand may include L-fields in all the sub-headers.

3g-(Format 3-2g) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 3FA to 3FEB, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 3g-(Format 3-2g) structure is largelydivided into a MAC CE part and a MAC SDU part. The MAC CEs may belocated at a front part of the MAC SDU part in the order in which theyare first generated, and even the MAC CEs may be located at a rear partof the MAC CE part in the order in which they are first generated. Inthe MAC SDU part, the segments of one MAC SDU (or RLC PDU or RLC SDU)may be located at the tail. The sub-header may include some of thevariables described in Table 3, and information other than the variablesdescribed in Table 3. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,MAC CE, and padding, in the order numbered on the sub-headers and thepayloads of the 3g-(Format 3-2g). For example, the header of the frontpart becomes the information indicating the payload of the rear part.The 3g-(Format 3-2g) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU. The 3g-(Format 3-2h) structure is the same as the3g-(Format 3-2g) structure and may include L-fields in all thesub-headers.

3g-(Format 3-2i) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 3FA to 3FEB, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 3g-(Format 3-2i) structure is dividedinto a MAC CE part that may be first generated, a MAC SDU part, and aMAC CE part that are generated later. The MAC CEs may be located at afront part of the MAC SDU part in the order in which they are firstgenerated, and even the MAC CEs may be located at a rear part of the MACCE part in the order in which they are first generated. However, a MACCE (or the MAC CE determined to have the high priority, the MAC CE priorto the MAC SDU, or the MAC CE satisfying the predetermined criterion)that may be generated in advance before being allocated the uplinkresource of the uplink is the MAC CE part that may be generated firstand may be located at the head of the MAC PDU, and the remaining MAC CEsare the MAC CE part that may be generated later and may be located atthe tail of the MAC PDU. In the MAC SDU part, the last segment of oneMAC SDU (or RLC PDU or RLC SDU) may be located at the head of the MACSDU part and the first segment of one MAC SDU (or RLC PDU or RLC SDU)may be located at the tail of the MAC SDU part. The sub-header mayinclude some of the variables described in Table 3, and informationother than the variables described in Table 3. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC CE, MAC SDU, and padding, in the ordernumbered on the sub-headers and the payloads of the 3g-(Format 3-2i).For example, the header of the front part becomes the informationindicating the payload of the rear part. The 3g-(Format 3-2i) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The3g-(Format 3-2j) structure is the same as the 3g-(Format 3-2i) structureand may include L-fields in all the sub-headers.

3g-(Format 3-2k) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 3FA to 3FEB, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the third MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The 3g-(Format 3-2k) structure is dividedinto a MAC CE part that may be first generated, a MAC SDU part, and aMAC CE part that are generated later. The MAC CEs may be located at afront part of the MAC SDU part in the order in which they are firstgenerated, and even the MAC CEs may be located at a rear part of the MACCE part in the order in which they are first generated. However, a MACCE (or the MAC CE determined to have the high priority, the MAC CE priorto the MAC SDU, or the MAC CE satisfying the predetermined criterion)that may be generated in advance before being allocated the uplinkresource of the uplink is the MAC CE part that may be generated firstand may be located at the head of the MAC PDU, and the remaining MAC CEsare the MAC CE part that may be generated later and may be located atthe tail of the MAC PDU. In the MAC SDU part, the segments of one MACSDU (or RLC PDU or RLC SDU) may be located at the tail of the MAC SDUpart. The sub-header may include some of the variables described inTable 3, and information other than the variables described in Table 3.The padding is stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 3g-(Format3-2k). For example, the header of the front part becomes the informationindicating the payload of the rear part. The 3g-(Format 3-2k) structureis characterized in that an L-field is not included in the lastsub-header. The receiving side may confirm the L-field value of theremaining sub-headers and subtract the L-field value from the entirelength of the MAC PDU to estimate the length of the MAC SDU. The3g-(Format 3-2l) structure is the same as the 3g-(Format 3-2k) structureand may include L-fields in all the sub-headers.

The first method for applying padding which can be applied to variouscases of the first MAC PDU structure described in FIG. 3E of the presentdisclosure, the second MAC PDU structure described in FIGS. 3FA to 3FEB,and the third MAC PDU structures described in FIGS. 3GA to 3GC, Thefirst padding application method is as follows.

FIGS. 3HA and 3HB illustrate a first method for applying paddingaccording to an embodiment of the present disclosure.

Referring to FIGS. 3HA and 3HB, it is assumed that the size of the MACsub-header for padding is fixed to 1 byte.

The first method for applying padding of the present disclosure is asfollows.

If a first condition is satisfied, the first method is applied to addpadding.

If a second condition is satisfied, the second method is applied to addpadding.

If a third condition is satisfied, the third method is applied to addpadding.

In this case, if the first condition is that the required size ofpadding is 1 byte.

In this case, if the second condition is that the required size ofpadding is 2 bytes.

In this case, if the third condition is that the required size ofpadding is 3 bytes.

In the first method, one MAC sub-header for padding having a size of 1byte is added to the head of the MAC header part. In the case of thethird MAC PDU structure, one MAC sub-header for padding having a size of1 byte is added to the head of the MAC PDU. The first method may beapplied to various cases of the first MAC PDU structure described inFIG. 3E, such as 3h-(Format 1-1), 3h-(Format 2-1), and 3h-(Format 3-1),the second MAC PDU structure described in FIGS. 3FA to 3FEB, and thethird MAC PDU structure described in FIGS. 3GA to 3GC.

In the second method, two MAC sub-headers for padding having a size of 1byte are added to the head of the MAC header part. In the case of thethird MAC PDU structure, two MAC sub-headers for padding having a sizeof 1 byte are added to the head of the MAC PDU. The second method may beapplied to various cases of the first MAC PDU structure described inFIG. 3E, such as 3h-(Format 1-2), 3h-(Format 2-2), and 3h-(Format 3-2).The second MAC PDU structure described in FIGS. 3FA, to 3FEB, and thethird MAC PDU structure described in FIGS. 3GA to 3GC.

In the third method, one MAC sub-header for padding having a size of 1byte is added at the tail of the MAC header part, and the paddingcorresponding to the remaining size excluding 1 byte from the requiredsize of padding is added to the tail of the MAC payload. In the case ofthe third MAC PDU structure, one MAC sub-header for padding having asize of 1 byte and the padding corresponding to the remaining sizeexcluding 1 byte from the required size of padding are added to the tailof the MAC PDU. The third method may be applied to various cases of thefirst MAC PDU structure described in FIG. 3E, such as 3h-(Format 1-3),3h-(Format 2-3), and 3h-(Format 3-3). The second MAC PDU structuredescribed in FIGS. 3FA to 3FEB, and the third MAC PDU structuredescribed in FIGS. 3GA to 3GC.

The second method for applying padding which can be applied to variouscases of the first MAC PDU structure described in FIG. 3E of the presentdisclosure, the second MAC PDU structure described in FIGS. 3FE to 3FEB,and the third MAC PDU structure described in FIGS. 3GA to 3GC is asfollows.

FIGS. 3IA and 3IB illustrate a second method for applying padding ofaccording to an embodiment of the present disclosure.

Referring to FIGS. 3IA and 3IB, it is assumed that the size of the MACsub-header for padding is fixed to 2 byte.

The second method for applying padding of the present disclosure is asfollows.

If a first condition is satisfied, the first method is applied to addpadding.

If a second condition is satisfied, the second method is applied to addpadding.

If a third condition is satisfied, the third method is applied to addpadding.

In this case, if the first condition is that the required size ofpadding is 1 byte.

In this case, if the second condition is that the required size ofpadding is 2 bytes.

In this case, if the third condition is that the required size ofpadding is 3 bytes.

In the first method, one MAC sub-header for padding having a size of 1byte is added to the tail of the MAC header part. In the case of thethird MAC PDU structure, one MAC sub-header for padding having a size of1 byte is added to the head of the MAC PDU. The first method may beapplied to various cases of the first MAC PDU structure described inFIG. 3E, such as 3i-(Format 1-1), 3i-(Format 2-1), and 3i-(Format 3-1),the second MAC PDU structure described in FIGS. 3FA to 3FEB, and thethird MAC PDU structure described in FIGS. 3GA to 3GC.

In the second method, two MAC sub-headers for padding having a size of 2bytes are added to the tail of the MAC header part. In the case of thethird MAC PDU structure, two MAC sub-headers for padding having a sizeof 1 byte are added to the head of the MAC PDU. The second method may beapplied to various cases of the first MAC PDU structure described inFIG. 3E, such as 3i-(Format 1-2), 3i-(Format 2-2), and 3i-(Format 3-2),the second MAC PDU structure described in FIGS. 3FA to 3FEB, and thethird MAC PDU structure described in FIGS. 3GA to 3GC.

In the third method, one MAC sub-header for padding having a size of 1byte is added at the tail of the MAC header part, and the paddingcorresponding to the remaining size excluding 1 byte from the requiredsize of padding is added to the tail of the MAC payload. In the case ofthe third MAC PDU structure, one MAC sub-header for padding having asize of 1 byte and the padding corresponding to the remaining sizeexcluding 1 byte from the required size of padding are added to the tailof the MAC PDU. The second method may be applied to various cases of thefirst MAC PDU structure described in FIG. 3E, such as 3i-(Format 1-3),3i-(Format 2-3), and 3i-(Format 3-3), the second MAC PDU structuredescribed in FIGS. 3FA to 3FEB, and the third MAC PDU structuredescribed in FIGS. 3GA to 3GC.

The third method for applying padding which can be applied to variouscases of the first MAC PDU structure described in FIG. 3E of the presentdisclosure, the second MAC PDU structure described in FIGS. 3FEA to3FEB, and the third MAC PDU structure described in FIGS. 3GA to 3GC isas follows.

FIG. 3J is a diagram illustrating a third method for applying paddingaccording to an embodiment of the present disclosure.

Referring to FIG. 3J, it is assumed that the size of the MAC sub-headerfor padding is fixed to 1 byte.

The third method for applying padding of the present disclosure is asfollows.

If a first condition is satisfied, the first method is applied to addpadding.

If a second condition is satisfied, the second method is applied to addpadding.

In this case, if the first condition is that the required size ofpadding is 1 byte.

In this case, if the third condition is that the required size ofpadding is 2 bytes.

In the above, the first method adds padding having a size of 1 byte tothe tail of the MAC PDU. In the case of the second MAC PDU structure,the padding having the size of 1 byte may be added to the tail of theMAC payload and thus the padding may be located in the middle of the MACPDU. In the case of the third MAC PDU structure, the padding having asize of 1 byte is added to the tail of the MAC PDU. The first method maybe applied to various cases of the first MAC PDU structure described inFIG. 3E, such as 3j-(Format 1-1), 3j-(Format 2-1), and 3j-(Format 3-1),the second MAC PDU structure described in FIGS. 3FA to 3FEB, and thethird MAC PDU structure described in FIGS. 3GA to 3GC.

In the second method, one MAC sub-header for padding having a size of 1byte is added at the tail of the MAC header part, and the paddingcorresponding to the remaining size excluding 1 byte from the requiredsize of padding is added to the tail of the MAC payload. In the case ofthe third MAC PDU structure, one MAC sub-header for padding having asize of 1 byte and the padding corresponding to the remaining sizeexcluding 1 byte from the required size of padding are added to the tailof the MAC PDU. The third method may be applied to various cases of thefirst MAC PDU structure described in FIG. 3E, such as 3j-(Format 1-2),3j-(Format 2-2), and 3j-(Format 3-2), the second MAC PDU structuredescribed in FIGS. 3FA to 3FEB, and the third MAC PDU structuredescribed in FIGS. 3GA to 3GC.

The fourth method for applying padding which can be applied to variouscases of the first MAC PDU structure described in FIG. 3E of the presentdisclosure, the second MAC PDU structure described in FIGS. 3FEA to3FEB, and the third MAC PDU structure described in FIGS. 3GA to 3GC isas follows.

FIG. 3K is a diagram illustrating a fourth method for applying paddingof according to an embodiment of the present disclosure.

Referring to FIG. 3K, it is assumed that the size of the MAC sub-headerfor padding is fixed to 2 bytes.

The fourth method for applying padding of the present disclosure is asfollows.

If a first condition is satisfied, the first method is applied to addpadding.

If a second condition is satisfied, the second method is applied to addpadding.

In this case, if the first condition is that the required size ofpadding is 1 byte or 2 bytes.

In this case, if the second condition is that the required size ofpadding is 3 bytes or more.

In the above, the first method adds padding having a size of 1 byte or 2bytes to the tail of the MAC PDU according to the required size ofpadding. In the case of the second MAC PDU structure, the padding havingthe size of 1 byte or 2 bytes may be added to the tail of the MACpayload according to the required size of padding and thus the paddingmay be located in the middle of the MAC PDU. In the case of the thirdMAC PDU structure, padding having a size of 1 byte or 2 bytes is addedto the head of the MAC PDU according to the required size of padding.The first method may be applied to various cases of the first MAC PDUstructure described in FIG. 3E, such as 3k-(Format 1-1), 3k-(Format2-1), and 3k-(Format 3-1), the second MAC PDU structure described inFIGS. 3FA to 3FEB, and the third MAC PDU structure described in FIGS.3GA to 3GC.

In the second method, one MAC sub-header for padding having a size of 2bytes is added to the tail of the MAC header part, and the paddingcorresponding to the remaining size excluding 2 bytes from the requiredsize of padding is added to the tail of the MAC payload. In the case ofthe third MAC PDU structure, one MAC sub-header for padding having asize of 2 bytes and the padding corresponding to the remaining sizeexcluding 1 byte from the required size of padding are added to the tailof the MAC PDU. The third method may be applied to various cases of thefirst MAC PDU structure described in FIG. 3E, such as 3k-(Format 1-2),3k-(Format 2-2), and 3k-(Format 3-2), the second MAC PDU structuredescribed in FIGS. 3FA to 3FEB, and the third MAC PDU structuredescribed in FIGS. 3GA to 3GC.

The second method for applying padding which can be applied to variouscases of the first MAC PDU structure described in FIG. 3E of the presentdisclosure, the second MAC PDU structure described in FIGS. 3FEA and3FEB, and the third MAC PDU structure described in FIGS. 3GA to 3GC isas follows.

In the fifth method for applying padding, it is assumed that the size ofthe MAC sub-header for padding is fixed to 1 byte.

The fifth method for applying padding of the present disclosure is asfollows.

If a first condition is satisfied, the first method is applied to addpadding.

If a second condition is satisfied, the second method is applied to addpadding.

If a third condition is satisfied, the third method is applied to addpadding.

In this case, if the first condition is that the required size ofpadding is 1 byte.

In this case, if the second condition is that the required size ofpadding is 2 bytes.

In this case, if the third condition is that the required size ofpadding is 3 bytes.

In the first method, one MAC sub-header for padding having a size of 1byte is added to the head of the MAC header part. In the case of thethird MAC PDU structure, one MAC sub-header for padding having a size of1 byte is added to any location of the MAC PDU. The first method may beapplied to various cases of the first MAC PDU structure described inFIG. 3E, such as 3h-(Format 1-1), 3h-(Format 2-1), and 3h-(Format 3-1),the second MAC PDU structure described in FIGS. 3FA to 3FEB, and thethird MAC PDU structure described in FIGS. 3GA to 3GC.

In the second method, two MAC sub-header for padding having a size of 2bytes are added to the head of the MAC header part. In the case of thethird MAC PDU structure, two MAC sub-headers for padding having a sizeof 1 byte are added to any location of the MAC PDU. The second methodmay be applied to various cases of the first MAC PDU structure describedin FIG. 3E, such as 3h-(Format 1-2), 3h-(Format 2-2), and 3h-(Format3-2). The second MAC PDU structure described in FIGS. 3FA to 3FEB, andthe third MAC PDU structure described in FIGS. 3GA to 3GC.

In the third method, one MAC sub-header for padding having a size of 1byte is added at any location of the MAC header part, and the paddingcorresponding to the remaining size excluding 1 byte from the requiredsize of padding is added to a location corresponding to the MACsub-header of the MAC payload part. In the case of the third MAC PDUstructure, one MAC sub-header for padding having a size of 1 byte andthe padding corresponding to the remaining size excluding 1 byte fromthe required size of padding are added to any location of the MAC PDU.The third method may be applied to various cases of the first MAC PDUstructure described in FIG. 3E, such as 3h-(Format 1-3), 3h-(Format2-3), and 3h-(Format 3-3). The second MAC PDU structure described inFIGS. 3FA to 3FEB, and the third MAC PDU structure described in FIGS.3GA to 3GC.

The sixth method for applying padding which can be applied to variouscases of the first MAC PDU structure described in FIG. 3E of the presentdisclosure, the second MAC PDU structure described in FIGS. 3FA to 3FEB,and the third MAC PDU structure described in FIGS. 3GA to 3GC is asfollows.

In the sixth method for applying padding, it is assumed that the size ofthe MAC sub-header for padding is fixed to 1 byte.

The sixth method for applying padding of the present disclosure is asfollows.

If a first condition is satisfied, the first method is applied to addpadding.

If a second condition is satisfied, the second method is applied to addpadding.

In this case, if the first condition is that the required size ofpadding is 1 byte.

In this case, if the second condition is that the required size ofpadding is 2 bytes or more.

In the above, the first method adds padding having a size of 1 byte toany location of the MAC PDU. In the case of the second MAC PDUstructure, padding having a size of 1 byte are added to any location ofthe MAC payload. In the case of the third MAC PDU structure, the paddinghaving a size of 1 byte is added to any location of the MAC PDU. Thefirst method may be applied to various cases of the first MAC PDUstructure described in FIG. 3E, such as 3j-(Format 1-1), 3j-(Format2-1), and 3j-(Format 3-1), the second MAC PDU structure described inFIGS. 3FA to 3FEB, and the third MAC PDU structure described in FIGS.3GA to 3GC.

In the second method, one MAC sub-header for padding having a size of 1byte is added at any location of the MAC header part, and the paddingcorresponding to the remaining size excluding 1 byte from the requiredsize of padding is added to a location corresponding to the padding MACsub-header of the MAC payload part. In the case of the third MAC PDUstructure, one MAC sub-header for padding having a size of 1 byte andthe padding corresponding to the remaining size excluding 1 byte fromthe required size of padding are added to any location of the MAC PDU.The third method may be applied to various cases of the first MAC PDUstructure described in FIG. 3E, such as 3j-(Format 1-2), 3j-(Format2-2), and 3j-(Format 3-2), the second MAC PDU structure described inFIGS. 3FA to 3FEB, and the third MAC PDU structure described in FIGS.3GA to 3GC.

The seventh method for applying padding which can be applied to variouscases of the first MAC PDU structure described in FIG. 3E of the presentdisclosure, the second MAC PDU structure described in FIGS. 3FEA to3FEB, and the third MAC PDU structure described in FIGS. 3GA to 3GC isas follows.

In the seventh method for applying padding, it is assumed that the sizeof the MAC sub-header for padding is fixed to 2 bytes.

The seventh method for applying padding of the present disclosure is asfollows.

If a first condition is satisfied, the first method is applied to addpadding,

If a second condition is satisfied, the second method is applied to addpadding.

In this case, if the first condition is that the required size ofpadding is 1 byte or 2 bytes.

In this case, if the second condition is that the required size ofpadding is 3 bytes or more.

In the above, the first method adds padding having a size of 1 byte or 2bytes to any location of the MAC PDU according to the required size ofpadding. In the case of the second MAC PDU structure, padding having asize of 1 byte or 2 bytes is added to any location of the MAC payloadaccording to the required size of padding. In the case of the third MACPDU structure, padding having a size of 1 byte or 2 bytes is added toany location of the MAC PDU according to the required size of padding.The first method may be applied to various cases of the first MAC PDUstructure described in FIG. 3E, such as 3k-(Format 1-1), 3k-(Format2-1), and 3k-(Format 3-1), the second MAC PDU structure described inFIGS. 3FA to 3FEB, and the third MAC PDU structure described in FIGS.3GA to 3GC.

In the second method, one MAC sub-header for padding having a size of 2byte is added at any location of the MAC header part, and the paddingcorresponding to the remaining size excluding 2 bytes from the requiredsize of padding is added to a location corresponding to the padding MACsub-header of the MAC payload part. In the case of the third MAC PDUstructure, one MAC sub-header for padding having a size of 2 byte andthe padding corresponding to the remaining size excluding 1 byte fromthe required size of padding are added to any location of the MAC PDU.The third method may be applied to various cases of the first MAC PDUstructure described in FIG. 3E, such as 3k-(Format 1-2), 3k-(Format2-2), and 3k-(Format 3-2), the second MAC PDU structure described inFIGS. 3FA to 3FEB, and the third MAC PDU structure described in FIGS.3GA to 3GC.

FIG. 3L is a diagram illustrating an operation of a terminal related tofirst, second, and fifth methods for applying padding according to anembodiment of the present disclosure.

Referring to FIG. 3L, if a terminal 3 l-01 satisfies the first conditionin operation 3 l-05, the process proceeds to operation 3 l-10 and thusthe padding is processed by the first method. If the second condition issatisfied in operation 3 l-05, the process proceeds to operation 3 l-15and thus the padding is processed by the second method. If the thirdcondition is satisfied in operation 3 l-05, the process proceeds tooperation 3 l-20 and thus the padding is processed by the third method.

FIG. 3M is a diagram illustrating an operation of a terminal related tothird, fourth, sixth, and seventh methods for applying padding accordingto an embodiment of the present disclosure.

Referring to FIG. 3M, if a terminal 3 m-01 satisfies the first conditionin operation 3 m-05, the process proceeds to operation 3 m-10 and thusthe padding is processed by the first method. If the second condition issatisfied in operation 3 m-05, the process proceeds to operation 3 m-15and thus the padding is processed by the second method.

FIG. 3N is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure.

Referring to FIG. 3N, the terminal includes a radio frequency (RF)processor 3 n-10, a baseband processor 3 n-20, a storage 3 n-30, and acontroller 3 n-40.

The RF processor 3 n-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 3 n-10 up-converts a baseband signalprovided from the baseband processor 3 n-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 3 n-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, adigital to analog converter (DAC), an analog to digital converter (ADC),or the like. FIG. 3n illustrates only one antenna but the terminal mayinclude a plurality of antennas. Further, the RF processor 3 n-10 mayinclude a plurality of RF chains. Further, the RF processor 3 n-10 mayperform beamforming. For the beamforming, the RF processor 3 n-10 mayadjust a phase and a size of each of the signals transmitted andreceived through a plurality of antennas or antenna elements. Inaddition, the RF processor may perform MIMO and may receive a pluralityof layers when performing the MIMO operation. The RF processor 3 n-10may perform reception beam sweeping by appropriately configuring aplurality of antennas or antenna elements under the control of thecontroller or adjust a direction and a beam width of the reception beamso that the reception beam is resonated with the transmission beam.

The baseband processor 3 n-20 performs a conversion function between abaseband signal and a bit string according to a physical layer standardof a system. For example, when data are transmitted, the basebandprocessor 3 n-20 generates complex symbols by coding and modulating atransmitted bit string. Further, when data are received, the basebandprocessor 3 n-20 recovers the received bit string by demodulating anddecoding the baseband signal provided from the RF processor 3 n-10. Forexample, according to the OFDM scheme, when data are transmitted, thebaseband processor 3 n-20 generates the complex symbols by coding andmodulating the transmitting bit string, maps the complex symbols tosub-carriers, and then performs an inverse fast Fourier transform (IFFT)operation and a cyclic prefix (CP) insertion to construct the OFDMsymbols. Further, when data are received, the baseband processor 3 n-20divides the baseband signal provided from the RF processor 3 n-10 in anOFDM symbol unit and recovers the signals mapped to the sub-carriers bya fast Fourier transform (FFT) operation and then recovers the receivedbit string by the modulation and decoding.

The baseband processor 3 n-20 and the RF processor 3 n-10 transmit andreceive a signal as described above. Therefore, the baseband processor 3n-20 and the RF processor 3 n-10 may be called a transmitter, areceiver, a transceiver, or a communication unit. Further, at least oneof the baseband processor 3 n-20 and the RF processor 3 n-10 may includea plurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 3 n-20 and the RF pocessor 3 n-10 may include differentcommunication modules to process signals in different frequency bands.For example, the different wireless access technologies may include anLTE network, an NR network, and the like. Further, different frequencybands may include a super high frequency (SHF) (for example: 2.5 GHz, 5GHz) band, a millimeter wave (for example: 60 GHz) band.

The storage 3 n-30 stores data, such as basic programs, applicationprograms, and configuration information for the operation of theterminal. Further, the storage 3 n-30 provides the stored data accordingto the request of the controller 3 n-40.

The controller 3 n-40 includes a multiple connection processor 3 n-42and controls the overall operations of the terminal. For example, thecontroller 3 n-40 transmits and receives a signal through the basebandprocessor 3 n-20 and the RF processor 3 n-10. Further, the controller 2i-40 records and reads data in and from the storage 2 i-40. For thispurpose, the controller 3 n-40 may include at least one processor. Forexample, the controller 3 n-40 may include a communication processor(CP) performing a control for communication and an application processor(AP) controlling an upper layer, such as the application programs.

FIG. 3O is a block configuration diagram of TRP in a wirelesscommunication system according to an embodiment of the presentdisclosure.

Referring to FIG. 3O, the base station is configured to include an RFprocessor 3 o-10, a baseband processor 3 o-20, a communication unit 3o-30, a storage 3 o-40, and a controller 3 o-50.

The RF processor 3 o-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 3 o-10 up-converts a baseband signalprovided from the baseband processor 3 o-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 3 o-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC,an ADC, or the like. FIG. 3O illustrates only one antenna but the firstaccess node may include a plurality of antennas. Further, the RFprocessor 3 o-10 may include a plurality of RF chains. Further, the RFprocessor 3 o-10 may perform the beamforming. For the beamforming, theRF processor 3 o-10 may adjust a phase and a size of each of the signalstransmitted/received through a plurality of antennas or antennaelements. The RF processor may perform a downward MIMO operation bytransmitting one or more layers.

The baseband processor 3 o-20 performs a conversion function between thebaseband signal and the bit string according to the physical layerstandard of the first radio access technology. For example, when dataare transmitted, the baseband processor 3 o-20 generates complex symbolsby coding and modulating a transmitted bit string. Further, when dataare received, the baseband processor 3 o-20 recovers the received bitstring by demodulating and decoding the baseband signal provided fromthe RF processor 3 o-10. For example, according to the OFDM scheme, whendata are transmitted, the baseband processor 3 o-20 generates thecomplex symbols by coding and modulating the transmitting bit string,maps the complex symbols to the sub-carriers, and then performs the IFFToperation and the CP insertion to construct the OFDM symbols. Further,when data are received, the baseband processor 3 o-20 divides thebaseband signal provided from the RF processor 3 o-10 in the OFDM symbolunit and recovers the signals mapped to the sub-carriers by the FFToperation and then recovers the receiving bit string by the modulationand decoding. The baseband processor 3 o-20 and the RF processor 3 o-10transmit and receive a signal as described above. Therefore, thebaseband processor 3 o-20 and the RF processor 3 o-10 may be called atransmitter, a receiver, a transceiver, or a communication unit.

The communication unit 3 o-30 provides an interface for performingcommunication with other nodes within the network.

The storage 3 o-40 stores data, such as basic programs, applicationprograms, and configuration information for the operation of the mainbase station. More particularly, the storage 3 o-40 may store theinformation on the bearer allocated to the accessed terminal, themeasured results reported from the accessed terminal, and the like.Further, the storage 3 o-40 may store information that is adetermination criterion on whether to provide a multiple connection tothe terminal or stop the multiple connection to the terminal. Further,the storage 3 o-40 provides the stored data according to the request ofthe controller 3 o-50.

The controller 3 o-50 includes a multiple connection processor 3 o-52and controls the general operations of the main base station. Forexample, the controller 3 o-50 transmits/receives a signal through thebaseband processor 3 o-20 and the RF processor 3 o-10 or thecommunication unit 3 o-30. Further, the controller 3 o-50 records andreads data in and from the storage 3 o-40. For this purpose, thecontroller 3 o-50 may include at least one processor.

Fourth Embodiment

FIG. 4A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure.

Referring to FIG. 4A, a radio access network of an LTE system isconfigured to include next generation base stations (evolved node B,hereinafter, eNB, Node B, or base station) 4 a-05, 4 a-10, 4 a-15, and 4a-20, a mobility management entity (MME) 4 a-25, and a serving-gateway(S-GW) 4 a-30. User equipment (hereinafter, UE or terminal) 4 a-35accesses an external network through the eNBs 4 a-05 to 4 a-20 and theS-GW 4 a-30.

Referring to FIG. 4A, the ENB 4 a-05 to 4 a-20 correspond to theexisting node B of the UMTS system. The eNB is connected to the UE 4a-35 through a radio channel and performs more complicated role than theexisting node B. In the LTE system, in addition to a real-time servicelike a voice over Internet protocol (VoIP) through the Internetprotocol, all the user traffics are served through a shared channel andtherefore an apparatus for collecting and scheduling status information,such as a buffer status, an available transmit power status, and achannel state of the terminals is required. Here, the eNBs 4 a-05 to 4a-20 take charge of the collecting and scheduling. One eNB generallycontrols a plurality of cells. For example, to implement a transmissionrate of 100 Mbps, the LTE system uses, as a radio access technology,OFDM, for example, in a bandwidth of 20 MHz. Further, an adaptivemodulation & coding (hereinafter, called AMC) determining a modulationscheme and a channel coding rate depending on the channel status of theterminal is applied. The S-GW 4 a-30 is an apparatus for providing adata bearer and generates or removes the data bearer according to thecontrol of the MME 4 a-25. The MME is an apparatus for performing amobility management function for the terminal and various controlfunctions and is connected to a plurality of base stations.

FIG. 4B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure.

Referring to FIG. 4B, the radio protocol of the LTE system is configuredto include PDCPs 4 b-05 and 4 b-40, RLCs 4 b-10 and 4 b-35, and mediumaccess controls (MMCs) 4 b-15 and 4 b-30 in the terminal and the eNB,respectively. The PDCPs 4 b-05 and 4 b-40 are in charge of operations,such as IP header compression/decompression. The main functions of thePDCP are summarized as follows.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUsat PDCP re-establishment procedure for RLC AM)

Reordering function (For split bearers in DC (only support for RLC AM):PDCP PDU routing for transmission and PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs atPDCP re-establishment procedure for RLC AM)

Retransmission function (Retransmission of PDCP SDUs at handover and,for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure,for RLC AM)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink.)

The RLCs 4 b-10 and 4 b-35 reconfigures the PDCP PDU to an appropriatesize to perform the ARQ operation or the like. The main functions of theRLC are summarized as follows.

Data transfer function (Transfer of upper layer PDUs)

ARQ function (Error Correction through ARQ (only for AM data transfer))

Concatenation, segmentation, reassembly functions (Concatenation,segmentation and reassembly of RLC SDUs (only for UM and AM datatransfer))

Re-segmentation function (Re-segmentation of RLC data PDUs (only for AMdata transfer))

Reordering function (Reordering of RLC data PDUs (only for UM and AMdata transfer)

Duplicate detection function (Duplicate detection (only for UM and AMdata transfer))

Error detection function (Protocol error detection (only for AM datatransfer))

RLC SDU discard function (RLC SDU discard (only for UM and AM datatransfer))

RLC re-establishment function (RLC re-establishment)

The MACs 4 b-15 and 4 b-30 are connected to several RLC layer apparatusconfigured in one terminal and perform an operation of multiplexing RLCPDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU.The main functions of the MAC are summarized as follows.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MACSDUs belonging to one or different logical channels into/from transportblocks (TB) delivered to/from the physical layer on transport channels)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

Physical layers 4 b-20 and 4 b-25 perform an operation of channel-codingand modulating higher layer data, making the upper layer data as an OFDMsymbol and transmitting them to a radio channel, or demodulating andchannel-decoding the OFDM symbol received through the radio channel andtransmitting the demodulated and channel-decoded OFDM symbol to theupper layer.

FIG. 4C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure.

Referring to FIG. 4C, a radio access network of a next generation mobilecommunication system is configured to include a next generation basestation (New radio node B, hereinafter NR gNB or NR base station) 4 c-10and a new radio core network (NR CN) 4 c-05. The user terminal (newradio user equipment, hereinafter, NR UE or UE) 4 c-15 accesses theexternal network through the NR gNB 4 c-10 and the NR CN 4 c-05.

Referring to FIG. 4C, the NR gNB 4 c-10 corresponds to an evolved node B(eNB) of the existing LTE system. The NR gNB 4 c-10 is connected to theNR UE 4 c-15 via a radio channel and may provide a service superior tothe existing node B. In the next generation mobile communication system,since all user traffics are served through a shared channel, anapparatus for collecting state information, such as a buffer state, anavailable transmit power state, and a channel state of the UEs toperform scheduling is required. The NR gNB 4 c-10 may serve as thedevice. One NR gNB 4 c-10 generally controls a plurality of cells. Inorder to realize high-speed data transmission compared with the existingLTE, the NR gNB may have an existing maximum bandwidth or more, and maybe additionally incorporated into a beam-forming technology may beapplied by using OFDM as a radio access technology 4 c-20. Further, anadaptive modulation & coding (hereinafter, referred to as AMC)determining a modulation scheme and a channel coding rate according to achannel status of the terminal is applied. The NR CN 4 c-05 may performfunctions, such as mobility support, bearer setup, QoS setup, and thelike. The NR CN is a device for performing a mobility managementfunction for the terminal and various control functions and is connectedto a plurality of base stations. In addition, the next generation mobilecommunication system can interwork with the existing LTE system, and theNR CN is connected to the MME 4 c-25 through the network interface. TheMME is connected to the eNB 4 c-30 which is the existing base station.

FIG. 4D is a diagram illustrating a DRX operation for an IDLE terminalin an LTE system according to an embodiment of the present disclosure.

Referring to FIG. 4D, the terminals 4 d-10 and 4 d-15 monitor the PDCCHto receive paging from the network 4 d-10 when being in the RRC IDLEstate. In the LTE, a discontinuous reception (hereinafter, referred toas DRX) interval is set in each subframe 4 d-20 unit by a method forefficiently reducing power consumption of a terminal, and the terminalawakes for a predetermined time interval and the receiver sleeps formost of the remaining time. For example, paging cycles 4 d-25 and 4d-30, which is a predetermined time interval, is set to receive pagingfrom the network 4 d-10. If the terminal detects a P-RNTI used forpaging, the terminals 4 d-10 and 4 d-15 process the correspondingdownlink paging message. The paging message includes an ID of theterminal, and terminals not corresponding to the ID discard the receivedinformation and sleep according to the DRX cycle. Since the uplinktiming is not known for the DRX cycle, HARQ is not used.

The network sets up a subframe 4 d-20 in which the terminal shouldreceive paging. For the setting, among a cycle Tue that the terminalrequests and a cell-specific period Tc, a minimum value is used. Inaddition, 32, 64, 128, and 256 frames are set in the paging cycle. Asubframe to be monitored for paging in the frame may be extracted fromthe international mobile subscriber identity (IMSI) of the terminal.Since each terminal has different IMSIs, it operates according to apaging instance belonging to each terminal at the entire paging occasion4 d-35.

The paging message may be transmitted only in some subframes, and showspossible settings in Table 4 below.

TABLE 4 The number of paging subframes 1/32 1/16 ⅛ ¼ ½ 1 2 4 Paging FDD9 9 9 9 9 9 4, 9 0, 4, 5, 9 subframe TDD 0 0 0 0 0 0 0, 5 0, 1, 5, 6

FIG. 4E is a diagram illustrating a DRX operation for a terminal in anRR connection state in an LTE system according to an embodiment of thepresent disclosure.

Referring to FIG. 4E, the DRX is defined even in the RRC connectionstate, and the operation method is different from the DRX in the IDLEstate. As described above, in order for the terminal to acquire thescheduling information, continuously monitoring the PDCCH will causelarge power consumption. The basic DRX operation has a DRX cycle 4 e-00and monitors the PDCCH only for an on-duration 4 e-05 time. In theconnection mode, the DRX cycle has two values, long DRX and short DRX.The long DRX cycle is applied in the general case. If necessary, thebase station may use a MAC control element (CE) to trigger the short DRXcycle. After the predetermined time has expired, the terminal is changedfrom the short DRX cycle to the long DRX cycle. The initial schedulinginformation of the specific terminal is provided only in thepredetermined PDCCH. Therefore, the terminal can periodically monitoronly the PDCCH, thereby minimizing the power consumption. If schedulinginformation for a new packet is received by the PDCCH (4 e-10) for theon-duration 4 e-05, the terminal starts a DRX inactivity timer 4 e-15.The terminal maintains an active state during the DRX inactivity timer.For example, the PDCCH monitoring is continued. In addition, the HARQRTT timer 4 e-20 also starts. The HARQ RTT timer is applied to preventthe terminal from unnecessarily monitoring the PDCCH during HARQ RTT(Round Trip Time), and the terminal does not need to perform the PDCCHmonitoring during the timer operation time. However, while the DRXinactivity timer and the HARQ RTT timer are operated simultaneously, theterminal continues to monitor the PDCCH based on the DRX inactivitytimer. If the HARQ RTT timer expires, the DRX retransmission timer 4e-25 starts. During the DRX retransmission timer operation, the terminalneeds to perform the PDCCH monitoring. Generally, during the DRXretransmission timer operation, the scheduling information for HARQretransmission is received (4 e-30). Upon receiving the schedulinginformation, the terminal immediately stops the DRX retransmission timerand starts the HARQ RTT timer again. The above operation continues untilthe packet is successfully received (4 e-35).

The configuration information related to the DRX operation in theconnection mode is transmitted to the terminal through theRRCConnectionReconfiguration message. The on-duration timer, the DRXinactivity timer, and the DRX retransmission timer are defined by thenumber of PDCCH subframes. After the timer starts, if the subframedefined by the PDCCH subframe passes by the set number, the timerexpires. In FDD, all downlink subframes belong to the PDCCH subframe,and in TDD, the downlink subframe and the special subframe correspondthereto. In the TDD, a downlink subframe, an uplink subframe, and aspecial subframe exist in the same frequency band. Among them, thedownlink subframe and the special subframe are regarded as the PDCCHsubframe.

The base station can set two states, longDRX and shortDRX. The basestation will normally use one of the two states based on powerpreference indication information and terminal mobility recordinginformation reported from the terminal, and set DRB characteristics. Thetransition between the two states is made by transmitting whether aspecific timer expires or not or a specific MAC CE to the terminal.

FIG. 4F is a diagram illustrating a DRX operation in an INACTIVE stateaccording to an embodiment of the present disclosure.

Referring to FIG. 4F, a terminal 4 f-01 and a base station 4 f-03transmits and receives data in the RRC connected (or RRC ACTIVE) state,in operation 4 f-05, and then the base station 4 f-03 may instruct thetransition to the inactive state of the terminal 4 f-01. The transitioncondition to the INACTIVE state may generate an event, or the likeaccording to the absence of a data packet and a measurement value of aradio link. In addition, in the RRC connected state, the terminal 4 f-01may be operated in a connected DRX (C-DRX) according to the setting ofthe base station 4 f-03. In operation 4 f-10, the base station 4 f-03instructs the transition from the RRC ACTIVE to the RRC INACTIVE statethrough an inactive reconfiguration message. The INACTIVEreconfiguration message includes the following information.

INACTIVE STATE information (RESUME ID, RAN Area info, . . . )

INACTIVE state DRX configuration parameter

More particularly, it may include configuration parameters for DRXoperation in the RRC INACTIVE state, and two operations will bedescribed in an embodiment of the present disclosure. A first DRXoperation in the INACTIVE state is operated similar to the DRX operationin the RRC IDLE state in the existing LTE. To this end, the INACTIVEreconfiguration message requires signaling to enable calculation of apaging frame (PF) and a paging occasion (PO) for each terminal. To thisend, it is possible to reuse a value (PCCH-config) set in the SIB2 ordirectly reconfigure the related parameters (paging cycle, the number nBof paging subframes per paging cycle). A second DRX operation in theINACTIVE state is operated similar to the connected DRX operation in theexisting LTE. The connected DRX operation has a plurality of DRX cycles(long DRX cycle, short DRX cycle), and a number of DRX timers(onDuration timer, inactivityTimer, and the like) are defined. Inaddition, the timer may be flexibly set for each DRX cycle. However, inthe INACTIVE state, the flexible setting from the base station 4 f-03 isrestrictive differently from the RRC connected state, and thereforethere is a need to introduce the restrictive method. For example, oneDRX cycle is set for the second DRX operation in the INACTIVE state(e.g., set only a long DRX cycle) and the short inactivity timer, theon-duration timer, or the like may be set as a predetermined value. Forthe case where the data transmission and reception is possible in theDRX operation in the INACTIVE state, the HARQ RTT timer, the DRXretransmission timer, or the like may also be set.

The terminal 4 f-01 performs DRX (I-DRX) in the INACTIVE state accordingto the method established from the base station 4 f-03 in operation 4f-15. If the terminal 4 f-01 receives a paging signal from the basestation 4 f-03 in operation 4 f-20), the terminal 4 f-01 stops the I-DRXoperation in operation 4 f-25.

The terminal 4 f-01 attempts a random access to the corresponding cellin operation 4 f-30. The random access is to fit an uplinksynchronization simultaneously with notifying a target cell that theterminal attempts a connection. After the preamble transmission in therandom access process, a certain number of subframes have passed, andthen the terminal 4 f-01 monitors whether or not a random accessresponse message (RAR) is transmitted from the cell. If the RAR isreceived for the specific time in operation 4 f-35, the terminal 4 f-01transmits Resume ID and Resume cause by carrying the Resume ID and theResume cause on RRCConnectionResumeRequest message in operation 4 f-40.In operation 4 f-45, the cell may confirm the Resume ID of the receivedmessage to know from which base station the corresponding terminalreceives a service before. If the base station 4 f-03 successfullyreceives and confirms the Resume ID, the UE context may be reused. (Ifthe base station receives the Resume ID but does not successfullyidentify the terminal, instead of the operations 4 f-40 to 4 f-55, anRRCConnectionSetup message may be delivered to the terminal instead ofin operations 4 f-40 to 4 f-55 and the operation may return to theexisting legacy RRC connection establishment procedure.) The basestation 4 f-03 applies the security information of the UE context andconfirms the integrity of the message using the MAC-I, the security keyand the security counter stored in the context of the UE, or the like.The base station 4 f-03 determines the configuration to be applied tothe RRC connection of the terminal 4 f-01 and transmits anRRConnectionResume message storing the configuration information to theterminal 4 f-01 in operation 4 f-50. The message may include C-DRXconfiguration information for the DRX operation in the connected state.The terminal configures the RRC connection by applying the updated UEcontext and the configuration information, and transmits the RRCconnection resumption completion message to the base station 4 f-03 andperforms the connection in operation 4 f-55.

FIG. 4G is a diagram illustrating an operation of a terminal forperforming a DRX in an INACTIVE state according to an embodiment of thepresent disclosure.

Referring to FIG. 4F, it is assumed that the terminal is alreadyconnected to the base station/cell in the connection mode and istransmitting/receiving data from the beam of the corresponding cell. Asdescribed above, the terminal in the connection mode may request thebase station to transition to the INACTIVE state for a specificsituation, and may be instructed to the transition to the INACTIVE stateaccording to the determination of the base station in operation 4 g-05.The example of the first case may include the case where the terminalmay measure the quality of the radio link with the base station/cell andreport a specific event, and in the second case, the base station maydetermine the case in which there is no the transmission/reception datapacket with the terminal for a while. The INACTIVE reconfigurationmessage includes the following information.

INACTIVE STATE information (RESUME ID, RAN Area info, . . . )

INACTIVE state DRX configuration parameter

More particularly, it may include configuration parameters for the DRXoperation in the RRC INACTIVE state, and may be divided into a firstoperation and a second operation according to an operation type and aparameter type set by the base station in operation 4 g-10. The basestation and the terminal may support only a predetermined operation, andmay support both operations. The first DRX operation in operation 4 g-15in the INACTIVE state is operated similar to the DRX operation in theRRC IDLE state in the existing LTE. The terminal calculates a pagingframe (PF) and a paging occasion (PO) for each terminal based on the DRXparameters received from the base station. The parameter may bePCCH-Config information transmitted in SIB2 or a value indicating thePCCH-Config information. The second DRX operation in operation 4 g-20 inthe INACTIVE state is operated similar to the connected DRX operation inthe existing LTE. The terminal sets the DRX cycle received from the basestation (set only one long DRX cycle) and sets the short inactivitytimer, the on-duration timer or the like. The above parameters may beset to be predetermined fixed value unlike the C-DRX in LTE. For thecase where the data transmission and reception is possible in the DRXoperation in the INACTIVE state, the HARQ RTT timer, the DRXretransmission timer, or the like may also be set. Thereafter, theterminal performs the INACTIVE DRX operation until receiving the paginginformation from the base station. If the paging information is receivedin operation 4 g-25 from the base station during the INACTIVE DRXoperation, the terminal stops the INACTIVE DRX operation and performsthe RRC connection recovery in operation 4 g-30. The Resume procedure orthe RRC connection reconfiguration procedure may be used to recover theRRC connection. The base station may include the parameters for the DRX(C-DRX) operation in the connection mode in the connection recoverypermission message, and the terminal performs the C-DRX operation basedon the received setting value in operation 4 g-35.

FIG. 4H is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure.

Referring to FIG. 4H, the terminal includes a radio frequency (RF)processor 4 h-10, a baseband processor 4 h-20, a storage 4 h-30, and acontroller 4 h-40.

The RF processor 4 h-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 4 h-10 up-converts a baseband signalprovided from the baseband processor 4 h-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 4 h-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, adigital to analog converter (DAC), an analog to digital converter (ADC),or the like. FIG. 4H illustrates only one antenna but the terminal mayinclude a plurality of antennas. Further, the RF processor 4 h-10 mayinclude a plurality of RF chains. Further, the RF processor 4 h-10 mayperform beamforming. For the beamforming, the RF processor 4 h-10 mayadjust a phase and a size of each of the signals transmitted andreceived through a plurality of antennas or antenna elements. Inaddition, the RF processor may perform MIMO and may receive a pluralityof layers when performing a MIMO operation.

The baseband processor 4 h-20 performs a conversion function between abaseband signal and a bit string according to a physical layer standardof a system. For example, when data are transmitted, the basebandprocessor 4 h-20 generates complex symbols by coding and modulating atransmitted bit string. Further, when data are received, the basebandprocessor 4 h-20 recovers the received bit string by demodulating anddecoding the baseband signal provided from the RF processor 4 h-10. Forexample, according to the OFDM scheme, when data are transmitted, thebaseband processor 4 h-20 generates the complex symbols by coding andmodulating the transmitting bit string, maps the complex symbols tosub-carriers, and then performs an inverse fast Fourier transform (IFFT)operation and a cyclic prefix (CP) insertion to construct the OFDMsymbols. Further, when data are received, the baseband processor 4 h-20divides the baseband signal provided from the RF processor 4 h-10 in anOFDM symbol unit and recovers the signals mapped to the sub-carriers bya fast Fourier transform (FFT) operation and then recovers the receivedbit string by the modulation and decoding.

The baseband processor 1 k-20 and the RF processor 1 k-10 transmit andreceive a signal as described above. Therefore, the baseband processor 4h-20 and the RF processor 4 h-10 may be called a transmitter, areceiver, a transceiver, or a communication unit. Further, at least oneof the baseband processor 4 h-20 and the RF processor 4 h-10 may includea plurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 4 h-20 and the RF processor 4 h-10 may include differentcommunication modules to process signals in different frequency bands.For example, different radio access technologies may include thewireless LAN (for example: IEEE 802.11), a cellular network (forexample: LTE), or the like. Further, different frequency bands mayinclude a super high frequency (SHF) (for example: 2 NRHz) band, amillimeter wave (for example: 60 GHz) band.

The storage 4 h-30 stores data, such as basic programs, applicationprograms, and configuration information for the operation of theterminal. More particularly, the storage 4 h-30 may store informationassociated with a second access node performing wireless communicationusing a second access technology. Further, the storage 4 h-30 providesthe stored data according to the request of the controller 4 h-40.

The controller 4 h-40 includes a multiple connection processor 4 h-42and controls the overall operations of the terminal. For example, thecontroller 4 h-40 transmits and receives a signal through the basebandprocessor 4 h-20 and the RF processor 4 h-10. Further, the controller 4h-40 records and reads data in and from the storage 4 h-40. For thispurpose, the controller 4 h-40 may include at least one processor. Forexample, the controller 4 h-40 may include a communication processor(CP) performing a control for communication and an application processor(AP) controlling an upper layer, such as the application programs.

FIG. 4I is a block diagram illustrating a configuration of an NR basestation according to according to an embodiment of the presentdisclosure.

Referring to FIG. 4I, the base station is configured to include an RFprocessor 4 i-10, a baseband processor 4 i-20, a backhaul communicationunit 4 i-30, a storage 4 i-40, and a controller 4 i-50.

The RF processor 4 i-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 4 i-10 up-converts a baseband signalprovided from the baseband processor 4 i-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 4 i-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC,an ADC, or the like. FIG. 4I illustrates only one antenna but the firstaccess node may include a plurality of antennas. Further, the RFprocessor 4 i-10 may include a plurality of RF chains. Further, the RFprocessor 4 i-10 may perform the beamforming. For the beamforming, theRF processor 4 i-10 may adjust a phase and a size of each of the signalstransmitted/received through a plurality of antennas or antennaelements. The RF processor may perform a downward MIMO operation bytransmitting one or more layers.

The baseband processor 4 i-20 performs a conversion function between thebaseband signal and the bit string according to the physical layerstandard of the first radio access technology. For example, when dataare transmitted, the baseband processor 4 i-20 generates complex symbolsby coding and modulating a transmitted bit string. Further, when dataare received, the baseband processor 4 i-20 recovers the received bitstring by demodulating and decoding the baseband signal provided fromthe RF processor 4 i-10. For example, according to the OFDM scheme, whendata are transmitted, the baseband processor 4 i-20 generates thecomplex symbols by coding and modulating the transmitting bit string,maps the complex symbols to the sub-carriers, and then performs the IFFToperation and the CP insertion to configure the OFDM symbols. Further,when data are received, the baseband processor 4 i-20 divides thebaseband signal provided from the RF processor 4 i-10 in the OFDM symbolunit and recovers the signals mapped to the sub-carriers by the FFToperation and then recovers the receiving bit string by the modulationand decoding. The baseband processor 4 i-20 and the RF processor 4 i-10transmit and receive a signal as described above. Therefore, thebaseband processor 4 i-20 and the RF processor 4 i-10 may be called atransmitter, a receiver, a transceiver, or a communication unit.

The backhaul communication unit 4 i-30 provides an interface forperforming communication with other nodes within the network. Forexample, the backhaul communication unit 4 i-30 converts bit stringstransmitted from the main base station to other nodes, for example, anauxiliary base station, a core network, and the like, into physicalsignals and converts the physical signals received from other nodes intothe bit strings.

The storage 4 i-40 stores data, such as basic programs, applicationprograms, and configuration information for the operation of the mainbase station. More particularly, the storage 4 i-40 may store theinformation on the bearer allocated to the accessed terminal, themeasured results reported from the accessed terminal, and the like.Further, the storage 4 i-40 may store information that is adetermination criterion on whether to provide a multiple connection tothe terminal or stop the multiple connection to the terminal. Further,the storage 4 i-40 provides the stored data according to the request ofthe controller 4 i-50.

The controller 4 i-50 includes a multiple connection processor 4 i-52and controls the general operations of the main base station. Forexample, the controller 4 i-50 transmits/receives a signal through thebaseband processor 4 i-20 and the RF processor 4 i-10 or the backhaulcommunication unit 4 i-30. Further, the controller 4 i-50 records andreads data in and from the storage 4 i-40. For this purpose, thecontroller 4 i-50 may include at least one processor.

The present disclosure has the right of the following claims.

Method for performing, by a terminal, discontinuous reception in aninactive state.

1. An operation of receiving an inactive reconfiguration when theterminal is transited from an RRC ACTIVE state to an RRC INACTIVE state

Method for including parameters required to perform a first DRXoperation in the INACTIVE state in the message;

Method for including parameters required to perform a second DRXoperation in the INACTIVE state in the message;

Method by which the first operation calculates PO/PF for each terminalsimilar to a DRX operation in an IDLE state and monitors PDCCH;

Method by which the second operation is similar to the DRX operation inthe RRC ACTIVE state but uses limited parameters;

Method by which the parameter includes a predetermined one DRX cycle,short drx-inactivityTimer, short onDurationTimer, or the like.

2. Method for performing, by a terminal, an INACTIVE DRX operation basedon a set value received from a base station

3. Method for stopping the INACTIVE DRX operation and performingtransition to the ACTIVE state if the terminal receives paging.

4. Method for performing, by a terminal, a RESUME procedure and resumingan ACTIVE DRX operation;

Method for performing, by the above procedure, a random access andtransmitting a resume request;

Method for including Resume ID and Resume cause in the Resume request;

Method for receiving a Resume permission message from a base station;

Method for including parameters for an ACTIVE DRX operation in themessage;

Method for transmitting a Resume complete message to the base station;

Fifth Embodiment

FIG. 5A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure.

Referring to FIG. 5A, a radio access network of an LTE system isconfigured to include next generation base stations (evolved node B,hereinafter, eNB, Node B, or base station) 5 a-05, 5 a-10, 5 a-15, and 5a-20, a mobility management entity (MME) 5 a-25, and a serving-gateway(S-GW) 5 a-30. A user equipment (hereinafter, UE or terminal) 5 a-35accesses an external network through the eNBs 5 a-05 to 5 a-20 and theS-GW 5 a-30.

Referring to FIG. 5A, the ENB 5 a-05 to 5 a-20 correspond to theexisting node B of the UMTS system. The eNB is connected to the UE 5a-35 through a radio channel and performs more complicated role than theexisting node B. In the LTE system, in addition to a real-time servicelike a voice over Internet protocol (VoIP) through the Internetprotocol, all the user traffics are served through a shared channel andtherefore an apparatus for collecting and scheduling status information,such as a buffer status, an available transmit power status, and achannel state of the terminals is required. Here, the eNBs 5 a-05 to 5a-20 take charge of the collecting and scheduling. One eNB generallycontrols a plurality of cells. For example, to implement a transmissionrate of 100 Mbps, the LTE system uses, as a radio access technology,OFDM, for example, in a bandwidth of 20 MHz. Further, an adaptivemodulation & coding (hereinafter, called AMC) determining a modulationscheme and a channel coding rate depending on the channel status of theterminal is applied. The S-GW 5 a-30 is an apparatus for providing adata bearer and generates or removes the data bearer according to thecontrol of the MME 5 a-25. The MME is an apparatus for performing amobility management function for the terminal and various controlfunctions and is connected to a plurality of base stations.

FIG. 5B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure.

Referring to FIG. 5B, the radio protocol of the LTE system is configuredto include PDCPs 5 b-05 and 5 b-40, RLCs 5 b-10 and 5 b-35, and mediumaccess controls (MMCs) 5 b-15 and 5 b-30 in the terminal and the eNB,respectively. The PDCPs 5 b-05 and 5 b-40 are in charge of operations,such as IP header compression/decompression. The main functions of thePDCP are summarized as follows.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUsat PDCP re-establishment procedure for RLC AM)

Reordering function (For split bearers in DC (only support for RLC AM):PDCP PDU routing for transmission and PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs atPDCP re-establishment procedure for RLC AM)

Retransmission function (Retransmission of PDCP SDUs at handover and,for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure,for RLC AM)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink)

The RLCs 5 b-10 and 5 b-35 reconfigures the PDCP PDU to an appropriatesize to perform the ARQ operation or the like. The main functions of theRLC are summarized as follows.

Data transfer function (Transfer of upper layer PDUs)

ARQ function (Error Correction through ARQ (only for AM data transfer))

Concatenation, segmentation, reassembly functions (Concatenation,segmentation and reassembly of RLC SDUs (only for UM and AM datatransfer))

Re-segmentation function (Re-segmentation of RLC data PDUs (only for AMdata transfer))

Reordering function (Reordering of RLC data PDUs (only for UM and AMdata transfer)

Duplicate detection function (Duplicate detection (only for UM and AMdata transfer))

Error detection function (Protocol error detection (only for AM datatransfer))

RLC SDU discard function (RLC SDU discard (only for UM and AM datatransfer))

RLC re-establishment function (RLC re-establishment)

The MACs 5 b-15 and 5 b-30 are connected to several RLC layer apparatusconfigured in one terminal and perform an operation of multiplexing RLCPDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU.The main functions of the MAC are summarized as follows.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MACSDUs belonging to one or different logical channels into/from transportblocks (TB) delivered to/from the physical layer on transport channels)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between Logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

Physical layers 5 b-20 and 5 b-25 perform an operation of channel-codingand modulating higher layer data, making the upper layer data as an OFDMsymbol and transmitting them to a radio channel, or demodulating andchannel-decoding the OFDM symbol received through the radio channel andtransmitting the demodulated and channel-decoded OFDM symbol to theupper layer.

FIG. 5C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure.

Referring to FIG. 5C, a radio access network of a next generation mobilecommunication system is configured to include a next generation basestation (New radio node B, hereinafter NR gNB or NR base station) 5 c-10and a new radio core network (NR CN) 5 c-05. The user terminal (newradio user equipment, hereinafter, NR UE or UE) 5 c-15 accesses theexternal network through the NR gNB 5 c-10 and the NR CN 5 c-05.

Referring to FIG. 5C, the NR gNB 5 c-10 corresponds to an evolved node B(eNB) of the existing LTE system. The NR gNB 5 c-10 is connected to theNR UE 5 c-15 via a radio channel and may provide a service superior tothe existing node B. In the next generation mobile communication system,since all user traffics are served through a shared channel, anapparatus for collecting state information, such as a buffer state, anavailable transmit power state, and a channel state of the UEs toperform scheduling is required. The NR gNB 5 c-10 may serve as thedevice. One NR gNB 5 c-10 generally controls a plurality of cells. Inorder to realize high-speed data transmission compared with the existingLTE, the NR gNB may have an existing maximum bandwidth or more, and maybe additionally incorporated into a beam-forming technology may beapplied by using OFDM as a radio access technology 5 c-20. Further, anadaptive modulation & coding (hereinafter, called AMC) determining amodulation scheme and a channel coding rate depending on a channelstatus of the terminal is applied. The NR CN 5 c-05 may performfunctions, such as mobility support, bearer setup, QoS setup, and thelike. The NR CN is a device for performing a mobility managementfunction for the terminal and various control functions and is connectedto a plurality of base stations. In addition, the next generation mobilecommunication system can interwork with the existing LTE system, and theNR CN is connected to the MME 5 c-25 through the network interface. TheMME is connected to the eNB 5 c-30 which is the existing base station.

FIG. 5D is a diagram illustrating new functions handling QoS in an NRsystem according to an embodiment of the present disclosure.

Referring to FIG. 5D, in the NR system, it is necessary to set a usertraffic transmission path or control an IP flow for each serviceaccording to services requesting different quality of service (QoS),that is, according to QoS requirement. In the NR system, a plurality ofQoS flows are mapped to a plurality of data radio bearers (DRBs) and mayset the bearers simultaneously. For example, since a plurality of QoSflows 5 d-01, 5 d-02, and 5 d-03 may be mapped to the same DRB or otherDRBs 5 d-10, 5 d-15, and 5 d-20 for the downlink, it is necessary tomark the QoS flow ID in the downlink packet to differentiate them. Theabove function is a function that does not exist in the existing LTEPDCP protocol and therefore a new protocol (AS Multiplexing Layer,hereinafter, ASML) 5 d-05, 5 d-40, 5 d-50, and 5 d-85 that is in chargeof the function is introduced or a new function needs to be added to thePDCP. The above-mentioned ASML protocol may be referred to as a servicedata adaptation protocol (SDAP) layer protocol. In addition, the markingpermits the terminal to implement the reflective QoS for the uplink. Asdescribed above, explicitly marking the QoS flow ID for the downlinkpacket is a simple method by which an access stratum (AS) of a terminalprovides the information to the NAS of the terminal. A method formapping IP flows to DRBs in a downlink may include the following twooperations.

AS level mapping: IP flow->QoS flow

AS level mapping: QoS flow->DRB

It is possible to understand the QoS flow mapping information andpresence/absence of the reflective QoS operation for each of thereceived DRBs 5 d-25, 5 d-30 in the downlink reception, and 5 d-35 andto transmit the corresponding information to the NAS, wherein QoS flow 1is 5 d-41, QoS flow 2 is 5 d-42, and QoS flow 3 is 5 d-43.

Similarly, the two-stage mapping may be used even for the uplink. First,the IP flows are mapped to the QoS flows through NAS signaling. Forexample, since a plurality of QoS flows 5 d-86, 5 d-87, and 5 d-88 maybe mapped to the same DRB or other DRBs 5 d-70, 5 d-75, and 5 d-80 forthe uplink, it is necessary to mark the QoS flow ID in the uplink packetto differentiate them. The QoS flows are then mapped to predeterminedDRBs 5 d-55, 5 d-60, and 5 d-65 in the AS. The terminal may mark the QoSflow ID for the uplink packet or may not mark the QoS flow ID for theuplink packet, and transmit the packet as it is. The function isperformed in the ASML of the terminal. If the QoS flow ID is marked forthe uplink packet, the base station may display the QoS flow ID for thepacket delivering the information to the NG-U without the uplink trafficflow template (TFT) and deliver the QoS flow ID.

The present disclosure describes a method for supporting new functionshandling QoS in an NR system and a method for designing ASML5 d-05, 5d-40, 5 d-50, and 5 d-85 for supporting the same. The above ASML 5 d-05,5 d-40, 5 d-50, and 5 d-85 is not a DRB-based protocol and QoS flow 1 is5 d-45, QoS flow 2 is 5 d-46, and QoS flow 3 is 5 d-47.

FIG. 5E is a first structure of an ASML protocol according to anembodiment of the present disclosure.

Referring to FIG. 5E, to handle a new QoS function of an NR system, thefollowing information needs to be delivered through a radio interface.

Downlink: QOS flow ID+reflective QOS processing required indicator

Uplink: QOS flow ID

An interface for delivering the new information as described above to Uuis required, and the first structure defines a new protocol forperforming the above function on the PDCP 5 e-10 layer. The ASML 5 e-05is not the DRB-based protocol, but a packet is transferred based on aDRB (5 e-30) mapping rule. For example, if IP traffic is generated, inthe ASML 5 e-05, the IP flow is mapped to the QoS flow ID and the QoSflow ID is mapped to the DRB. Here, the IP traffic consists of an IPheader 5 e-35 and a payload 5 e-40, and an ASML header 5 e-45 may belocated after the IP packet and located before the IP packet. If theASML header 5 e-45 is located before the IP packet, length informationof the ASML header 5 e-45 is required when a header compression isperformed in the PDCP 5 e-10, and therefore an overhead occurs, but theASML header 5 e-45 may be located before the IP packet. In the PDCP 5e-10, an IP header 5 e-55 is compressed and a PDCP header 5 e-50 isadded. Even in the RLC 5 e-15 and the MAC 5 e-20, the respective RLCheader 5 e-60 and the MAC header 5 e-65 are sequentially added and theMAC PDU is transferred to the PHY 5 e-25.

FIG. 5F is a diagram illustrating an ASML header in a first structure ofan ASML according to an embodiment of the present disclosure.

Referring to FIG. 5F, the first ASML structure is to introduce anindependent protocol that performs new functions on the PDCP layer. Asthe method for designing the ASML header, it is conceivable to include afull QoS flow ID of 8 bits or 16 bits for all downlink packets. Sincethe QoS flow ID consists of bytes, it may have a length of 8 bits or 16bits. However, in this case, it is necessary to perform the followingreflective QoS update operation for all downlink packets.

Reflective QoS update operation 1 (AS)

Confirm whether the uplink QoS flow of the received downlink packet ismapped to the DRB that receives the packet

If the above condition is not satisfied, update the uplink QoS flow tobe mapped to the DRB receiving the downlink packet

Reflective QoS update operation 2 (NAS)

Confirm whether the uplink QoS flow of the received downlink packet ismapped to the QoS flow that receives the packet

If the above condition is not satisfied, update the uplink QoS flow tobe mapped to the DRB receiving the downlink packet (uplink TFT update)

Performing the above operation every time all the downlink packets arereceived not only causes considerable processing consumption but also isunnecessary. Mapping for the IP flow or the QoS flow is only needed ifthe QoS requirements are different and this may not occur often.Therefore, we propose two ASML header configuration methods to reducethe above overhead.

Option 1 (consisting of 1-byte header)

Use short QoS flow ID 5 f-05 (e.g., 4 bits) having a shorter length thanFull QoS flow ID (8 or 16 bits)

The 1-bit reflective QoS indicator (RQ) 5 f-10 is included in thedownlink packet to instruct the terminal to perform the reflective QoSupdate operation

Set the remaining bits of the header as reserved bits (R) 5 f-15

Option 2-1 (header length varies conditionally)

The QoS flow ID 5 f-30 is included in the downlink packet only when theterminal needs to perform the reflective QoS update operation.

Include a 1-bit RQ indicator 5 f-20 informing whether the packetincludes the QoS flow ID

Set the remaining bits of the header to reserved bits (R) 5 f-25

For the above option 1, the base station transmits the mappinginformation between the QoS flow ID and the short QoS flow ID to theterminal through the RRC message (included in the DRB configurationmessage). The mapping information includes the mapping information tothe DRB.

In the option 2-2, the 1-bit RQ indicator may be included or may not beincluded or only the QoS flow ID 5 f-35 may also be included.

FIG. 5G is a diagram illustrating an operation of a terminal of a firststructure of an ASML according to an embodiment of the presentdisclosure.

Referring to FIG. 5G, the first ASML structure is to introduce anindependent protocol that performs new functions on the PDCP layer. TheASML is not the DRB-based protocol, and if the IP traffic is generated,the ASML marks the QoS flow ID and the reflective QoS indicator andtransfers the packet to the PDCP layer.

The terminal receives the RRC message for setting the DRB from the basestation in operation 5 g-05. As the RRC connection, RRC reconfiguration(re-) establishment and RRC reconfiguration are used. In addition, themessage also includes the following configuration information.

PDCP, RLC, logical channel configuration information (PDCPconfiguration, RLC configuration, LCH configuration)

Downlink ASML configuration information (ASML for DL): QOS flowID+reflective QOS indicator

Uplink ASML configuration information (ASML for UL): QOS flow ID

The mapping information between the full QoS flow ID and the short QoSflow ID to be used for DRB mapping (Mapping info from QoS flow ID toshort QoS flow ID)

The ASML exists as an independent layer and needs to be separately setfor each data transmission direction and DRB. In addition, the short QoSflow ID mapping information is used as information for mapping the shortQoS flow ID and the corresponding DRB when the first option is operated.The terminal receives the downlink MAC PDU from the base station inoperation 5 g-10, and transfers the RLC PDU demultiplexing the MAC PDUto the corresponding logical channel. The RLC PDU is processed as a PDCPPDU and delivered to the corresponding PDCP. The PDCP PDU is processedas a PDCP SDU. If the downlink ASML is set for the DRB, the ASML headerattached to the tail of the PDCP SDU is searched in operation 5 g-15.

If the ASML is set, the short QoS ID and the reflective QoS indicator ofthe corresponding packet are decoded and the following reflective QoSoperation is performed in operation 5 g-20.

Reflective QoS update operation 1 (AS)

Confirm whether the uplink QoS flow of the received downlink packet ismapped to the DRB that receives the packet

If the above condition is not satisfied, update the uplink QoS flow tobe mapped to the DRB receiving the downlink packet

Reflective QoS update operation 2 (NAS)

Confirm whether the uplink QoS flow of the received downlink packet ismapped to the QoS flow that receives the packet

If the above condition is not satisfied, update the uplink QoS flow tobe mapped to the DRB receiving the downlink packet

If the ASML is not set for the DRB or is not for the downlink althoughbeing set, the terminal transfers the PDCP SDU to the upper layer inoperation 5 g-25.

In operation 5 g-30, the terminal generates the IP packet for the uplinktransmission. If the ASML is set for the DRB for the uplink in operation5 g-35, the terminal generates the ASML header, attaches the generatedASML header to the IP packet in operation 5 g-40, and transfers thepacket to the PDCP layer of the DRB mapped to the QoS flow in operation5 g-45.

If ASML is not set for the DRB or the ASML is not set for the uplinkalthough being set, DRB, the terminal transfers the packet to the PDCPlayer of the DRB mapped to the QoS flow in operation 5 g-50.

In operation 5 g-55, the terminal processes the PDCP PDU as the RLC PDUpayload, attaches the RLC PDU header before the RLC payload, andtransmits the RLC PDU header to the corresponding logical channel. TheMAC PDU multiplexing the RLC PDU is generated and transmitted to the PHYin operation 5 g-60.

FIG. 5H is a second structure of an ASML protocol according to anembodiment of the present disclosure.

Referring to FIG. 5H, to handle a new QoS function of an NR system, thefollowing information needs to be transferred through a radio interface.

Downlink: QOS flow ID+reflective QOS processing required indicator

Uplink: QOS flow ID

An interface for transferring new information as described above to Uuis required, and a second structure introduces a PDCP-ASML 5 h-10sublayer which is in charge of the above function in the PDCP (5 h-05)layer and a PDCP Low-1, a PDCP Low-2, a PDCP Low-3 sublayer 5 h-15. Forexample, if the IP traffic is generated, the PDCP header including theQOS flow ID and the reflective QoS indicator is added to the IP packetin addition to the existing PDCP header in the PDCP 5 h-05. Here, the IPpacket consists of the IP header and the payload. In even the RLC 5 h-20and the MAC 5 h-25, the RLC header and the MAC header are sequentiallyadded and the MAC PDU is transferred to the PHY 5 h-30. The packet istransferred based on a DRB (5 h-35) mapping rule set in the PDCP-ASMLsublayer.

FIG. 5I is a diagram illustrating a PDCP header in a second structure ofan ASML according to an embodiment of the present disclosure.

Referring to FIG. 5I, the second ASML structure is to introduce aPDCP-ASML sublayer, which is in charge of new functions, into the PDCP.As the method for designing the PDCP header including the PDCP-ASML, inaddition to the existing D/C bit (data or control signal indicator) 5i-05, sequence number (SN) 5 i-15 bits, and the reserved bits 5 i-10, itcan be considered to include the full QoS flow ID of 8 bits or 16 bits.Since the QoS flow ID consists of bytes, it may have a length of 8 bitsor 16 bits. However, in this case, it is necessary to perform thefollowing reflective QoS update operation for all downlink packets.

Reflective QoS update operation 1 (AS)

Confirm whether the uplink QoS flow of the received downlink packet ismapped to the DRB that receives the packet

If the above condition is not satisfied, update the uplink QoS flow tobe mapped to the DRB receiving the downlink packet

Reflective QoS update operation 2 (NAS)

Confirm whether the uplink QoS flow of the received downlink packet ismapped to the QoS flow that receives the packet

If the above condition is not satisfied, update the uplink QoS flow tobe mapped to the DRB receiving the downlink packet (uplink TFT update)

Performing the above operation every time all the downlink packets arereceived not only causes considerable processing consumption but also isunnecessary. Mapping for the IP flow or the QoS flow is only needed ifthe QoS requirements are different and this may not occur often.Therefore, we propose two ASML header configuration methods to reducethe above overhead.

Option 1

Use short QoS flow ID 5 i-20 (e.g., 3 and 4 bits) having a shorterlength than Full QoS flow ID (8 or 16 bits)

The 1-bit reflective QoS indicator (RQ) 5 i-25 is included in thedownlink packet to instruct the terminal to perform the reflective QoSupdate operation

Set SN bits (10 or 11 bits) 5 i-35

Set the remaining bits of the header as reserved bits 5 i-30

Option 2 (header length varies conditionally)

The QoS flow ID 5 i-60 is included in the downlink packet only when theterminal needs to perform the reflective QoS update operation.

Include a 1-bit RQ indicator 5 i-45 informing whether the packetincludes the QoS flow ID

Set SN bits (10 or 11 bits) 5 i-55

Set the remaining bits of the header as reserved bits 5 i-50

For the above option 1, the base station transmits the mappinginformation between the QoS flow ID and the short QoS flow ID to theterminal through the RRC message (included in the DRB configuration,specifically, PDCP configuration message). The mapping informationincludes the mapping information to the DRB.

In the option 2, the 1-bit RQ indicator may be included or may not beincluded and may be used as a reserved bit 5 g-50.

In addition, under the certain conditions, the PDCP may be transmittedin the existing LTE structure (consisting of 5 i-05, 5 i-10, and 5 i-15)rather than the option 1 and option 2. This corresponds to the case whenthe reflective QoS update operation is not required.

FIG. 5J is a diagram illustrating an operation of a terminal of a secondASML structure according to an embodiment of the present disclosure.

Referring to FIG. 5J, the second ASML structure is to introduce aPDCP-ASML sublayer, which is in charge of new functions, into the PDCP.The PDCP-ASML is not a DRB-based sublayer, but is performed prior toprocessing of the existing PDCP header.

The terminal receives the RRC message for setting the DRB from the basestation in operation 5 j-05. As the RRC connection, RRC reconfiguration(re-) establishment and RRC reconfiguration are used. In addition, themessage also includes the following configuration information.

PDCP, RLC, logical channel configuration information (PDCPconfiguration, RLC configuration, LCH configuration)

The PDCP may include or may not include the following QoS relatedinformation.

Whether the QoS flow ID and the reflective QoS indicator are included

The mapping information between the full QoS flow ID and the short QoSflow ID to be used for DRB mapping (Mapping info from QoS flow ID toshort QoS flow ID)

The ASML exists as an independent layer and needs to be separately setfor each data transmission direction and DRB. In addition, the short QoSflow ID mapping information is used as information for mapping the shortQoS flow ID and the corresponding DRB when the first option is operated.The terminal receives the downlink MAC PDU from the base station inoperation 5 j-10, and transfers the RLC PDU demultiplexing the MAC PDUto the corresponding logical channel. The RLC PDU is processed as a PDCPPDU and transferred to the corresponding PDCP.

In operation 5 j-15, the terminal determines whether the QoS informationfor the DRB in the corresponding direction is included in the PDCPconfiguration, and decodes the QoS flow ID and the RQ if it is included,performs deciphering and header decompression, and then performs thefollowing reflective QoS operation in operation 5 j-20.

Reflective QoS update operation 1 (AS)

Confirm whether the uplink QoS flow of the received downlink packet ismapped to the DRB that receives the packet

If the above condition is not satisfied, update the uplink QoS flow tobe mapped to the DRB receiving the downlink packet

Reflective QoS update operation 2 (NAS)

Confirm whether the uplink QoS flow of the received downlink packet ismapped to the QoS flow that receives the packet

If the above condition is not satisfied, update the uplink QoS flow tobe mapped to the DRB receiving the downlink packet (uplink TFT update)

If operated as the option 1 to decode the QoS flow ID and RQ, theterminal may decode b1 to b4 of the first byte of the PDCP header, andif operated as the option 2, the terminal decodes the QoS flow ID thatis added after b1 and SN of the first byte of the PDCP header.

If no QoS information is included in the PDCP for the DRB in thecorresponding direction, the terminal performs the deciphering and theheader decompression on the PDCP PDU, and then processes the PDCP PDU asa PDCP SDU, which is then transmitted to the upper layer in operation 5j-25. If the terminal is operated as the option 1 in the aboveoperation, b1 to b4 of the first byte of the PDCP header are replacedwith 0 bits, and if the terminal is operated as the option 2, the PDCPheader is transferred in the same form as the PDCP header in theexisting LTE.

In operation 5 g-30, the terminal generates the IP packet for the uplinktransmission.

If the PDCP setting for the uplink DRB includes the QoS information inoperation 5 j-35, the terminal determines the QoS flow in operation 5i-40 and performs the header compression and the ciphering in operation5 i-45. In the above operation, when the terminal is operated as theoption 1, the QoS ID and the RQ bit are added to b1 to b4 of the firstbyte of the PDCP header, and if the terminal is operated as theoperation 2, the RQ bit is added to b1 of the first byte of the PDCPheader and add the full QoS flow ID added after the SN.

If no QoS information is included in the PDCP for the DRB in thecorresponding direction, the terminal performs the ciphering and theheader decompression on the PDCP PDU in operation 5 i-50, and thenprocesses the PDCP PDU as a PDCP SDU, which is then transmitted to theupper layer in operation 5 i-55.

In operation 5 j-60, the terminal processes the PDCP PDU as the RLC PDUpayload, attaches the RLC PDU header before the RLC payload, andtransmits the RLC PDU header to the corresponding logical channel. TheMAC PDU multiplexing the RLC PDU is generated and transmitted to the PHY(5 j-60).

FIG. 5K is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure.

Referring to FIG. 5K, the terminal includes a radio frequency (RF)processor 5 k-10, a baseband processor 5 k-20, a storage 5 k-30, and acontroller 5 k-40.

The RF processor 1 k-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 5 k-10 up-converts a baseband signalprovided from the baseband processor 5 k-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 5 k-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, adigital to analog converter (DAC), an analog to digital converter (ADC),or the like. FIG. 5K illustrates only one antenna but the terminal mayinclude a plurality of antennas. Further, the RF processor 5 k-10 mayinclude a plurality of RF chains. Further, the RF processor 5 k-10 mayperform beamforming. For the beamforming, the RF processor 5 k-10 mayadjust a phase and a size of each of the signals transmitted andreceived through a plurality of antennas or antenna elements. Inaddition, the RF processor may perform MIMO and may receive a pluralityof layers when performing the MIMO operation.

The baseband processor 5 k-20 performs a conversion function between abaseband signal and a bit string according to a physical layer standardof a system. For example, when data are transmitted, the basebandprocessor 5 k-20 generates complex symbols by coding and modulating atransmitted bit string. Further, when data are received, the basebandprocessor 1 k-20 recovers the received bit string by demodulating anddecoding the baseband signal provided from the RF processor 1 k-10. Forexample, according to the OFDM scheme, when data are transmitted, thebaseband processor 2 i-20 generates the complex symbols by coding andmodulating the transmitting bit string, maps the complex symbols tosub-carriers, and then performs an inverse fast Fourier transform (IFFT)operation and a cyclic prefix (CP) insertion to construct the OFDMsymbols. Further, when data are received, the baseband processor 4 h-20divides the baseband signal provided from the RF processor 4 h-10 in anOFDM symbol unit and recovers the signals mapped to the sub-carriers bya fast Fourier transform (FFT) operation and then recovers the receivedbit string by the modulation and decoding.

The baseband processor 5 k-20 and the RF processor 5 k-10 transmit andreceive a signal as described above. Therefore, the baseband processor 4h-20 and the RF processor 4 h-10 may be called a transmitter, areceiver, a transceiver, or a communication unit. Further, at least oneof the baseband processor 5 k-20 and the RF processor 5 k-10 may includea plurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 5 k-20 and the RF processor 5 k-10 may include differentcommunication modules to process signals in different frequency bands.For example, different radio access technologies may include thewireless LAN (for example: IEEE 802.11), a cellular network (forexample: LTE), or the like. Further, different frequency bands mayinclude a super high frequency (SHF) (for example: 2 NRHz) band, amillimeter wave (for example: 60 GHz) band.

The storage 5 k-30 stores data, such as basic programs, applicationprograms, and configuration information for the operation of theterminal. More particularly, the storage 5 k-30 may store informationassociated with a second access node performing wireless communicationusing a second access technology. Further, the storage 5 k-30 providesthe stored data according to the request of the controller 5 k-40.

The controller 5 k-40 includes a multiple connection processor 5 k-42and controls the overall operations of the terminal. For example, thecontroller 5 k-40 transmits and receives a signal through the basebandprocessor 5 k-20 and the RF processor 5 k-10. Further, the controller 5k-40 records and reads data in and from the storage 5 k-30. For thispurpose, the controller 5 k-40 may include at least one processor. Forexample, the controller 5 k-40 may include a communication processor(CP) performing a control for communication and an application processor(AP) controlling an upper layer, such as the application programs.

FIG. 5I is a block diagram illustrating a configuration of an NR basestation according to an embodiment of the present disclosure.

Referring to FIG. 5I, the base station is configured to include an RFprocessor 5I-10, a baseband processor 5I-20, a backhaul communicationunit 5I-30, a storage 5I-40, and a controller 5I-50.

The RF processor 5I-10 serves to transmit/receive a signal through aradio channel, such as band conversion and amplification of a signal.For example, the RF processor 5I-10 up-converts a baseband signalprovided from the baseband processor 5I-20 into an RF band signal andthen transmits the baseband signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 5I-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC,an ADC, and the like. FIG. SI illustrates only one antenna but the firstaccess node may include a plurality of antennas. Further, the RFprocessor 5I-10 may include the plurality of RF chains. Further, the RFprocessor 5I-10 may perform the beamforming. For the beamforming, the RFprocessor 5I-10 may adjust a phase and a size of each of the signalstransmitted and received through a plurality of antennas or antennaelements. The RF processor may perform a downward MIMO operation bytransmitting one or more layers.

The baseband processor 5I-20 performs a conversion function between thebaseband signal and the bit string according to the physical layerstandard of the first radio access technology. For example, when dataare transmitted, the baseband processor 5I-20 generates complex symbolsby coding and modulating a transmitting bit string. Further, when dataare received, the baseband processor 5I-20 recovers the receiving bitstring by demodulating and decoding the baseband signal provided fromthe RF processor 5I-10. For example, according to the OFDM scheme, whendata are transmitted, the baseband processor 5I-20 generates the complexsymbols by coding and modulating the transmitting bit string, maps thecomplex symbols to the sub-carriers, and then performs the IFFToperation and the CP insertion to configure the OFDM symbols. Further,when data are received, the baseband processor 5I-20 divides thebaseband signal provided from the RF processor 5I-10 in an OFDM symbolunit and recovers the signals mapped to the sub-carriers by an FFToperation and then recovers the receiving bit string by the modulationand decoding. The baseband processor 5I-20 and the RF processor 5I-10transmit and receive a signal as described above. Therefore, thebaseband processor 5I-20 and the RF processor 5I-10 may be called atransmitter, a receiver, a transceiver, a communication unit, or awireless communication unit.

The backhaul communicator 5I-30 provides an interface for performingcommunication with other nodes within the network. For example, thebackhaul communication unit 5I-30 converts bit strings transmitted fromthe main base station to other nodes, for example, an auxiliary basestation, a core network, and the like, into physical signals andconverts the physical signals received from other nodes into the bitstrings.

FIG. 5L is a block diagram illustrating a configuration of an NR basestation according to an embodiment of the present disclosure.

Referring to FIG. 5L, the storage 5I-40 stores data, such as basicprograms, application programs, and configuration information for theoperation of the main base station. More particularly, the storage 5I-40may store the information on the bearer allocated to the accessedterminal, the measured results reported from the accessed terminal, andthe like. Further, the storage 5I-40 may store information that is adetermination criterion on whether to provide a multiple connection tothe terminal or stop the multiple connection to the terminal. Further,the storage 5I-40 provides the stored data according to the request ofthe controller 5I-50.

The controller 5I-50 includes a multiple connection processor 5I-52 andcontrols the general operations of the main base station. For example,the controller 5I-50 transmits/receives a signal through the basebandprocessor 5I-20 and the RF processor 5I-10 or the backhaul communicator5I-30. Further, the controller 5I-50 records and reads data in and fromthe storage 5I-40. For this purpose, the controller 5I-50 may include atleast one processor.

A user plane protocol structure and operation of a terminal forsupporting flow-based service quality

1 Method for receiving an RRC message for setting a DRB from a basestation

The message includes PDCP, RLC, and logical channel;

The message includes AMSL setting values for each uplink and downlink;

The message includes mapping information between full QoS flow ID andshort QoS flow ID for being used DRB mapping;

2. Method for receiving a downlink packet and performing a reflectiveQoS update operation

The terminal receives a downlink MAC PDU and then configures a PDCP SDU;

The terminal differently performs reception and decoding according to anASML protocol structure;

If the terminal is operated in the first ASML structure, the decoding isperformed according to the QoS configuration information of the ASML;

The first ASML structure in which ASML exists on the PDCP as anindependent layer and the QoS flow ID and the reflective QoS indicatorinformation bit are included after the IP packet;

If the terminal is operated the second ASML structure, the decoding isperformed according to the QoS configuration information of the PDCP;

The second ASML structure includes the ASML function in the PDCP, andincludes the QoS flow ID and the reflective QoS indicator informationbit in the PDCP header;

The information bit of the ASML and the PDCP header is designed to havedifferent form according to the operation option;

The option 1 is designed to use the short QoS flow ID instead of thefull QoS flow ID;

The mapping information between the full QoS flow ID and the short QoSflow ID is received from the base station through an RRC message;

The option 2 includes the QoS flow ID and the reflective QoS indicatorinformation bits in the PDCP header only if the reflective QoS operationis required, and transfers the QoS flow ID and the reflective QoSindicator information bits in the PDCP header form of the existing LTE;

The terminal is requested to perform a reflective QoS update andperforms the reflective QoS update operation on the AS and the NAS;

In the AS reflective QoS update operation, it is confirmed whether theuplink QoS flow of the received downlink packet is mapped to the DRBthat receives the packet, and then if the condition is not satisfied,the uplink QoS flow is updated to be mapped to the DRB receiving thedownlink packet;

In the NAS reflective QoS update operation, it is confirmed whether theuplink QoS flow of the received downlink packet is mapped to the QoSflow that receives the packet, and then if the condition is notsatisfied, the uplink IP flow is updated to be mapped to the QoS flowreceiving the downlink packet;

If no ASML configuration information exists in the DRB in thecorresponding direction, the terminal transfers the PDCP SDU to theupper layer without further processing;

3. A method for generating and transmitting a data packet based on QoSconfiguration information if an uplink IP packet is generated

The terminal constructs transmission packets differently according tothe structure of the ASML protocol and transfers the transmissionpackets;

The uplink ASML includes only the QoS flow ID information;

If the terminal is operated in the first ASML structure, the decoding isperformed according to the QoS configuration information of the ASML;

If the terminal is operated in the ASML first structure, the QoS flow IDfor the corresponding DRB is attached after the IP packet by being addedto the ASML header and then is transferred to the upper layer;

If the terminal is operated in the second ASML structure, the decodingis performed according to the QoS configuration information of the PDCP;

If the terminal is operated in the second ASML structure, the QoS flowID for the corresponding DRB is attached after the IP packet by beingadded to the ASML header and then is transferred to the upper layer;

The information bit of the ASML and the PDCP header is designed to havedifferent forms according to the operation option;

The option 1 is designed to use the short QoS flow ID instead of thefull QoS flow ID;

The option 2 includes the QoS flow ID in the PDCP header only when thereflective QoS operation is performed and transfers the QoS flow ID inthe PDCP header form of the existing LTE if the reflective QoS operationis not performed;

The PDCP PDU including the ASML header is constructed as the MAC PDU andis transferred;

Sixth Embodiment

In an embodiment of the present disclosure, dual-registered means thatone terminal is simultaneously registered in two or more differentmobile communication systems to receive a service. In the existing LTEsystem, the terminal may be in a standby mode or a connection mode atthe RRC level in the registered state, i.e., the EMM-registered state.It is assumed that the present disclosure has a similar structure in thenext generation mobile communication system. The dual-registeredtechnology may be used for inter-system handover or direct carriertechnology between heterogeneous systems.

FIG. 6A is a diagram illustrating an inter-system handover by applyingdual-registered in a next generation mobile communication systemaccording to an embodiment of the present disclosure.

In an inter-system handover of the related art, the source systemrequests handover to the target system using the backhaul network. Inresponse to this, if the target system approves the request, the targetsystem prepares a radio resource for the handover terminal, andtransmits the configuration information necessary for the handover tothe source system. The source system provides configuration informationnecessary for the handover to a mobile station moving to the targetsystem. If the dual-registered technology is applied to the inter-systemhandover, the terminal performs attach to the target system instead ofperforming a handover procedure when moving from a previously connectedsystem to another system (6 a-50) according to the related art.

Referring to FIG. 6A, in an embodiment of the present disclosure, thebase station of the next generation mobile communication system isreferred to as gNB 6 a-25, and the base station of the LTE system isreferred to as eNB 6 a-30. The attach 6 a-40 means a procedure for theterminal 6 a-45 to register itself in the system. At this time, theterminal 6 a-45 may maintain the connection to the existing sourcesystem as it is. The advantage of the dual-registered technology doesnot require interoperability which applied to the existing handovertechnology between the source system 6 a-10 and the target system 6a-15. This can minimize the definition of interfaces between thesystems, thereby minimizing the upgrade of the existing system, and alsoreducing the signaling overhead between the systems. In order to supportthe dual-registered technology, the network of the source system 6 a-10and the target system 6 a-15 is connected to an NW entity called acommon IP anchor 6 a-20, and the common IP anchor 6 a-20 serves to routedata transmitted from the data network 6 a-05 to one terminal 6 a-45.Maintaining connection with an existing source system may vary dependingon the capabilities of the terminal 6 a-45. If the terminal 6 a-45 has aplurality of radios, it is not necessary to disconnect the source system6 a-25 according to the limitation of the number of radios. Typically,in the existing LTE system, the attach operation requires severalhundred milliseconds (ms). Therefore, if the necessary data istransmitted and received while maintaining the connection with theexisting source system (6 a-35), the service disconnection does notoccur during the attach operation (6 a-40) period. On the other hand, ifthe terminal has only one radio, the connection with the source systemwill be restricted. This is because the single radio should be appliedto the target system in the middle of performing the attach operation 6a-40 with the target system 6 a-15, so that the service may berestricted from the source system 6 a-10. However, even in this case,the connection with the source system may still be maintained (6 a-35)by the time division method (TDM). However, the service quality, such asthe delay time and the transmission rate may be somewhat lowered.

FIG. 6B is a diagram illustrating a signaling flow chart when a terminalmoves to a service area of an LTE system of the related art in a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 6B, a terminal 6 b-02 in a service area of a gNB 6b-04 exchanges capability of supporting dual-registered with each otherin operation 6 b-13. The gNB informs terminals within the service areawhether the next generation mobile communication system supportsdual-registered using system information to be broadcast. The terminaluses dedicated signaling to inform the gNB whether it supportsdual-registered.

The gNB sets the LTE frequency measurement to the terminal supportingthe dual-registered in operation 6 b-14. The configuration informationincludes a period for which the LTE frequency is measured and a timeperiod for which the LTE frequency for each measurement period ismeasured. The terminal receiving the configuration information maymeasure the LTE frequency during the predetermined time interval at eachpredetermined period in operation 6 b-16. Alternatively, the LTEfrequency may be measured at an appropriate time determined by theterminal itself. An example of the appropriate time is a time intervalduring which data is not transmitted to or received from the gNB. Inorder to measure the LTE frequency, the terminal turns-on an LTE modem.A terminal having a dual radio may keep the LTE modem, which is operatedonce, in an operation state and may turn-on the LTE modem every time theLTE frequency is measured and then turn-off the LTE modem when themeasurement is completed. Alternatively, the terminal supporting thedual-registered may measure the LTE frequency without being set from thegNB. In this case, however, the LTE frequency may be measured only at anappropriate time determined by the terminal itself. The terminal reportsthe measured result to the gNB in operation 6 b-18. The gNB determineswhether to set dual-registered or inter-RAT handover based on themeasurement result and other information in operation 6 b-20. The gNBsets the dual-registered to the terminal in operation 6 b-22. At thistime, a dedicated control plane message (dual-registered initialization)is used. The terminal receiving the message performs thedual-registered. At this time, the message may indicate the frequency orcell of the LTE system to which the terminal should attempt to attach.Alternatively, a list of frequencies or cells may be provided, and theterminal may attempt attach by selecting one of the frequencies or cellsbelonging to the list. The frequency or the cell is represented by afrequency bandwidth, center frequency information, and a cell ID(Physical cell ID or ECGI). In addition, in order to reduce the timethat the terminal attaches, the message may also include some systeminformation of the LTE system cell. The some system information isinformation necessary for the terminal to access the target system. Theessential system information is system information belonging to the MIB,SIB1, SIB2, SIB3, SIB4, and SIB5 broadcast by the LTE cell. Morespecifically, the essential system information may include a PLMN listsupported by the LTE system cell, a tracking area code, a closedsubscriber croup (CSG) cell ID, a frequency band list and spectrumemission information supported by the target system cell, accessprohibit-related information (e.g., ACB, EAB, SSAC, ACDC), configurationinformation related to a random access to the LTE system cell, cellreselection prioritization, and the like. The essential systeminformation of the LTE system cell is reported while the terminalreports the cell measurement according to the request of the gNB, or thegNB may always collect the system information on neighboring LTE systemcells from specific terminals within the service area using the SONtechnology. The terminal receiving the dual-registered initializationstarts a specific timer in operation 6 b-24. If the terminal receivingthe dual-registered initialization has the dual radio, the terminal canattach to the LTE system while maintaining the connection with the gNB.It means that the dual radio and two RF chains are included. If theterminal has a single radio, only one communication modem may transmitand receive data at a time. Therefore, if it is desired to maintain aconnection with the gNB, it should be maintained in the time divisionscheme. The terminal having the single radio may disconnect the gNB whenperforming the attach operation to then LTE system. If the specificprocess (attach process to the target LTE system) is not completed untilthe timer expires, the dual-registered process is considered to havefailed. The success of the attach to the target LTE system is determinedby whether an RRC message including an attach accept message is receivedfrom an MME 6 b-10. The terminal may acquire the system informationbroadcast directly from the target LTE cell (eNB 6 b-06) in operation 6b-26. The terminal attempts the random access to the target LTE cell inoperation 6 b-28. If it fails to acquire the essential systeminformation of the target LTE cell or fails to attempt the random accessof the predetermined number of times, the failure may be reported to thegNB in operation 6 b-30. The gNB receiving the failure report maytrigger the inter-RAT handover or retry the dual-registered with anotherLTE frequency or cell. The failure report may include the frequencyinformation or cell ID information that failed to the access and a causeof the failure. The possible causes of the failure may include systeminformation acquisition failure, random access failure, the expirationof the specific timer, or the like. The terminal transmits an attachrequest message to the MME 6 b-10 using the NAS container of the RRCconnection setup complete message while performing the RRC connectionestablishment process in operation 6 b-32 with the target LTE cell inoperation 6 b-34. At this time, the attach request message includes anindicator indicating that the terminal performs the dual-registered withthe LTE system. In addition, it may further indicate whether the dualregistration is for inter-RAT mobility support or for inter-RATaggregation. The inter-RAT mobility support may support the movement ofone terminal from one source system to a service area of another system.The inter-RAT aggregation provides services to a terminal connected toone system by being additionally connected to another system for thepurpose of improvement in throughput performance. The MME 6 b-10receiving the attach request message including the indicator performs S5session establishment and requests a common IP anchor 6 b-12 to routethe data to be transmitted to the next generation system to the LTEsystem in operation 6 b-36. The inter-RAT mobility support transmits alldata to the target system when the common IP anchor 6 b-12 performs arouting change. On the other hand, in the case of the inter-RATaggregation, when the common IP anchor 6 b-12 performs the routingchange, only a part of data is transmitted to the target system, andsome data are still transmitted to the source system. The common IPanchor 6 b-12 may change the entire data flow or some data flowtransmitted to the LTE system to the next generation system in operation6 b-44) and inform an NG core 6 b-08 that the data routing setting hasbeen changed in operation 6 b-46. The NG core 6 b-08 may inform the gNBof the change and allow the gNB to instruct a connection release for theterminal in operation 6 b-48. Alternatively, the data transmissionstops, and thus it may implicitly inform the NG core 6 b-08 that thedata routing has changed. If data is no longer transmitted from thegateway to the gNB, the gNB will disconnect from the terminal after acertain time has elapsed. The MME 6 b-10 successfully receiving theattach request message transmits an attach accept message to theterminal in operation 6 b-38. The terminal receiving the messageconsiders that the dual-registered operation is successfully completed.At this time, the terminal stops the timer. As one option, afterreceiving the attach accept message, the terminal may inform the gNBthat the dual-registered is successfully completed using a specificmessage in operation 6 b-40. The gNB receiving the message releases theconnection with the terminal in operation 6 b-42. After the completionof the dual-registered process, the disconnection with the nextgeneration system may have a terminal implementation aspect. If theterminal continuously wants to maintain the connection with the nextgeneration system, the uplink data are generated. If a radio linkfailure (RLF) occurs as in the existing LTE in the connection with thenext generation system after the dual-registered operation issuccessfully completed, the terminal instructs whether the terminal isbeing dual-registered in the report according to the RLF after RLFdeclaration or does not report the RLF to the next generation system.

FIG. 6C is a diagram illustrating a signaling flow chart when a terminalmoves to a service area of an LTE system of the related art in a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 6C, a terminal 6 c-02 in a service area of an eNB 6c-04 exchanges capability of supporting dual-registered with each otherin operation 6 c-13. The eNB informs terminals within the service areawhether the LTE system supports dual-registered using system informationto be broadcast. The terminal uses UECapabilitylnformation, which isdedicated signaling, to inform the eNB whether it supports thedual-registered.

The eNB sets the measurement for the next generation mobilecommunication (new radio (NR)) frequency to the terminal supportingdual-registered in operation 6 c-14. The configuration informationincludes a period for which the next generation mobile communicationfrequency is measured and a time period for which the next generationmobile communication frequency for each measurement period is measured.The terminal receiving the configuration information may measure thenext generation mobile communication frequency during the predeterminedtime interval at each predetermined period in operation 6 c-16.Alternatively, the next generation mobile communication frequency may bemeasured at an appropriate time determined by the terminal itself. Anexample of the appropriate time is a time interval during which data isnot transmitted to or received from the gNB. In order to measure thenext generation mobile communication frequency, the terminal turns-on anext generation mobile communication modem. A terminal having a dualradio may keep the next generation mobile communication modem, which isoperated once, in an operation state and may turn-on the next generationmobile communication modem every time the next generation mobilecommunication frequency is measured and then turn-off the nextgeneration mobile communication modem when the measurement is completed.Alternatively, the terminal supporting the dual-registered may measurethe next generation mobile communication frequency without being setfrom the eNB. In this case, however, the next generation mobilecommunication frequency may be measured only at an appropriate timedetermined by the terminal itself. The terminal reports the measuredresult to the eNB in operation 6 c-18. The gNB determines whether to setdual-registered or inter-RAT handover based on the measurement resultand other information in operation 6 b-20. The eNB sets thedual-registered to the terminal in operation 6 c-22. At this time, theRRCConnectionReconfiguration or RRCConnectionRelease message is used.More particularly, since the terminal receiving the RRCConnectionReleasemessage releases the connection with the source cell, when the sourcecell is determined, the terminal performs the source cell only when itis determined that it is desirable to release the connection with theterminal. For example, if the terminal has a single radio and thus it isdifficult to connect the terminal to both systems at the same time, andif it does not support the function of connecting both systems to eachother by the time division scheme, the terminal transmits theRRCConnectionRelease message. The terminal receiving at least one of themessages performs the dual-registered. At this time, the messages mayindicate the frequency or cell of the next generation mobilecommunication system of which the terminal should attempt the attach.Alternatively, a list of frequencies or cells may be provided, and theterminal may attempt attach by selecting one of the frequencies or cellsbelonging to the list. The frequency or the cell is represented by afrequency bandwidth, center frequency information, and a cell ID(Physical cell ID or ECGI). In addition, in order to reduce the timethat the terminal attaches, the message may also include some systeminformation of the next generation mobile communication system cell (gNB6 c-06). The some system information is information necessary for theterminal to access the target system. More specifically, the essentialsystem information may include a PLMN list supported by the nextgeneration mobile communication system cell, a tracking area code, aclosed subscriber croup (CSG) cell ID, a frequency band list andspectrum emission information supported by the target system cell,access prohibit-related information (e.g., ACB, EAB, SSAC, ACDC),configuration information related to a random access to the LTE systemcell, cell reselection prioritization, and the like. The essential nextgeneration mobile system information of the LTE system cell is reportedwhile the terminal reports the cell measurement according to the requestof the eNB, or the eNB may always collect the system information onneighboring next generation mobile communication system cells fromspecific terminals within the service area using the SON technology. Theterminal receiving the dual-registered initialization starts a specifictimer in operation 6 c-24. If the specific process (attach process tothe target next generation mobile communication system) is not completeduntil the timer expires, the dual-registered process is considered tohave failed. The success of the attach to the target next generationmobile communication system is determined by whether an RRC messageincluding an attach accept message is received from the MME 6 c-08. Theterminal may acquire the system information broadcast directly from thetarget next generation mobile communication cell in operation 6 c-26.The terminal attempts the random access to the target next generationmobile communication cell in operation 6 c-28. If it fails to acquirethe essential system information of the target next generation mobilecommunication cell or fails to attempt the random access of thepredetermined number of times, the failure may be reported to the eNB inoperation 6 c-30. The eNB receiving the failure report may trigger theinter-RAT handover or retry the dual-registered with another nextgeneration mobile communication frequency or cell. The failure reportmay include the frequency information or cell ID information that failedto the access and a cause of the failure. The possible causes of thefailure may include system information acquisition failure, randomaccess failure, the expiration of the specific timer, or the like. Theterminal transmits the attach request message to an NG core 6 c-10 usingthe NAS container of the specific control plane message while performingthe connection establishment process in operation 6 c-32 with the targetnext generation mobile communication cell in operation 6 c-34. At thistime, the attach request message includes an indicator indicating thatthe terminal performs the dual-registered with the next generationmobile communication system. The NG core 6 c-10 receiving the attachrequest message including the indicator performs S5 sessionestablishment and requests the common IP anchor 6 c-12 to route the datato be transmitted to the LTE to the next generation mobile communicationsystem in operation 6 c-36. The common IP anchor 6 c-12 requested maychange the entire data flow or some data flow transmitted to the nextgeneration mobile communication system to the LTE system in operation 6c-44 and inform the MME 6 c-08 that the data routing setting has beenchanged in operation 6 c-46. The MME 6 c-08 may inform the eNB of thechange and allow the eNB to instruct a connection release for theterminal in operation 6 c-48. Alternatively, the data transmissionstops, and thus it may implicitly inform the MME 6 c-08 that the datarouting has changed. If data is no longer transmitted from the gatewayto the eNB, the eNB will disconnect from the terminal after a certaintime has elapsed. The MME 6 c-08 successfully receiving the attachrequest message transmits an attach accept message to the terminal inoperation 6 c-38. The terminal receiving the message considers that thedual-registered operation is successfully completed. At this time, theterminal stops the timer. As one option, after receiving the attachaccept message, the terminal may inform the eNB that the dual-registeredis successfully completed using a specific message in operation 6 c-40.The gNB receiving the message releases the connection with the terminalin operation 6 c-42. After the completion of the dual-registeredprocess, the disconnection with the LTE system may have a terminalimplementation aspect. If the terminal continuously wants to maintainthe connection with the LTE system, the uplink data are generated. If aradio link failure (RLF) occurs in the connection with the LTE systemafter the dual-registered operation is successfully completed, theterminal instructs whether the terminal is being dual-registered in therelated RLF report after RLF declaration or does not report the RLF tothe LTE system.

FIG. 6D is a diagram illustrating a process of determininginitialization of a dual-registered operation according to an embodimentof the present disclosure.

Referring to FIG. 6D, the source system determines that the terminalneeds to be connected to another system based on the measurementinformation and various other information reported from the specificterminal in operation 6 d-02. In operation 6 d-04, the source systemdetermines whether an interface for interworking with the other systemis implemented. It is assumed that the interface is essential forsupporting the inter-RAT handover, which means at least one interfacebetween the NG Core and the MME, between the gNB and the MME, andbetween the NG Core and the eNB. If the interface is present, theinter-RAT handover may be supported, so that the handover may be set tothe terminal in operation 6 d-10. Otherwise, the dual-registeredoperation needs to be set. Even if the source system has the interface,it is possible to set the dual-registered operation for the purpose ofreducing the signaling overhead. In operation 6 d-06, it is determinedwhether the terminal supports the dual radio. The terminal reports theinformation to the source system in advance. If the terminal has thedual radio, in operation 6 d-16, the terminal performs the attach to thetarget system while maintaining the connection with the current systemas it is. The reason for maintaining the connection is totransmit/receive data even during the attach, thereby eliminating theservice disconnection. If the terminal does not have the dual radio, inoperation 6 d-08, it determines whether the source system and theterminal support a time division solution. The time division solution isa technique of transmitting and receiving data with one system at amoment. It may be assumed that the terminal supporting thedual-registered have to also support the time division solution. If thetime division solution is supported, in operation 6 d-14, the connectionwith the source system is maintained and data is transmitted andreceived in the time division scheme. The timing of transmitting andreceiving data between the source system and the target system mayoverlap. In this case, data transmission/reception with one system isperformed according to a predetermined rule. If the time divisionsolution is not supported, in operation 6 d-12, the connection with thesource system is released and the attach operation is performed.

FIG. 6E is a diagram illustrating a process of providing, by a terminal,information used for a source system according to an embodiment of thepresent disclosure.

Referring to FIG. 6E, a relatively long time is required for theterminal with the dual-registered to complete the attach to the targetsystem. This means the long service disconnection for the terminal thatdoes not support dual radio. Therefore, a method for reducing time forperforming an attach operation may be considered. Further, in order toaccess the cell, it is determined whether the cell is a suitable cell,and the access may be performed only if it is regarded as a suitablecell. Therefore, if the attach to a cell that is considered to be asuitable cell is attempted before triggering the dual-registered, theaccess failure probability and the attach time may be reduced. In orderto determine whether the cell is suitable, several conditions should besatisfied as follows. The information necessary for confirming the abovecondition is provided to the terminal as the system information (forexample, SIB1 in the LTE).

PLMN check

Operator specific barring

Forbidden TA (Tracking Area) check

Minimum radio condition (i.e., criterion S)

A method for attempting an attach to a cell which is regarded as asuitable cell in advance is as follows.

Option 1: The terminal 6 e-35 collects (6 e-10) the system informationbroadcast by the cell 6 e-15 of the target system in advance and reportsthe collected system information to the cell 6 e-05 of the source system(6 e-20). The cell of the source system determines the cell to beregarded as the suitable cell of the UE using the information, and setsthe cell to be dual-registered with the target cell (6 e-25).

Since the system information is not frequently changed information, thecell of the source system may collect the system information through theterminals in the service area using the SON technology.

Option 2: The terminal collects the system information broadcast by thecell of the target system in advance and reports the list of cells,which is regarded as the suitable cell, to the cells of the sourcesystem. The cell of the source system is set to be dual-registered withone cell or a plurality of cells in the list. The terminal performs thedual-registered with one of the one or more target cells.

The dual registration may also be used for inter-RAT aggregationpurposes to improve throughput performance of the terminal. If thesource system wishes to improve the throughput performance of aparticular terminal through the simultaneous transmission and receptionof data with another system, the source system triggers the dualregistration. However, the target system may already be in a networkcongestion state by servicing many terminals. Therefore, if the dualregistration is performed on such a target system, the above object willnot be achieved. Accordingly, the terminal collects access barringinformation from the system information of the target system and reportsthe access barring information to the source system. This allows thesource system to determine whether the target system is in the networkcongestion state. If a normal network congestion state occurs, the basestation controls it through access barring. Alternatively, informationthat may accurately indicate the network congestion state in the targetsystem may be broadcast by being included in the system information. Theterminal collecting the information reports it to the source system sothat the source system may use it to determine the trigger of the dualregistration.

FIG. 6F is a diagram illustrating a process of confirming access barringbefore a terminal performs an attach operation to a target cellaccording to an embodiment of the present disclosure.

Referring to FIG. 6F, in the target system 6 f-10, it may also bedesirable to suppress the access connection to the terminal performingthe dual-registration in order to control the congestion situation inthe network. If the dual-registered is set in the LTE system (6 f-20),the terminal may use the existing LTE access barring mechanism. Forexample, before the random access is attempted, it may be determinedwhether the cell is barring using the access barring configurationinformation 6 f-15 broadcast by the cell of the target LTE system (6f-30). Alternatively, the access barring configuration information ofthe cell of the target LTE system collected in advance by the sourcecell may be received together with the dual-registered configurationinformation to determine whether the cell is barring. If the target cell6 f-05 is considered to be barred by the barring check, it reports thatthe dual-registered operation failed due to the access barring to thesource cell (6 f-25). The existing LTE access barring mechanism refersto ACB, EAB, SSAC and ACDC, and at least one of them is applied. Inaddition to the existing barring mechanism, a separate barring mechanismmay be considered for the terminal that performs the dual-registered.

The target system may also want to control inter-frequency loading forthe terminal that performs the dual-registered. For this purpose, in theexisting LTE system, frequency-cell reselection priority information isprovided to the terminal, and the cell is reselected based on theinformation. The priority information may be broadcast by allowing acell to use system information or may be set to a specific cell bydedicated signaling.

One method is to allow the cell performing the dual-registered to usecell reselection priority information applied in the target system.Option 1: The terminal collects cell reselection priority informationthat is broadcast from neighboring systems. The collected information isreported to the source system. The source system sets a target frequencyat which the terminal performs the dual-registered based on the priorityinformation.

Option 2: The terminal collects cell reselection priority informationthat is broadcast from neighboring systems. The source system provides acandidate list of neighboring target cells to the terminal irrespectiveof the priority information. The candidate list may be determined basedon the cell measurement result. The terminal considers the collectedpriority information and selects one of the cells included in the listas the target cell. The target cell may be considered not only priorityinformation but also cell measurement information.

If the terminal has both the cell reselection priority informationbroadcast and the priority information provided as the dedicatedsignaling, the terminal performs the above operation based on thepriority information provided as the dedicated signaling.

FIG. 6G is a diagram illustrating a method for performing, by aterminal, an uplink power control according to an embodiment of thepresent disclosure.

Referring to FIG. 6G, the terminal that performs the dual-registered mayexperience a phenomenon of transmit power shortage in the uplink. Moreparticularly, since most of the area performed by the dual-registered isthe boundary area of the cell, higher transmit power may be required inthe uplink. In the case of the terminal having the dual radio, data canbe transmitted and received between two cells at the same time duringthe dual-registered operation, and if the data transmission timingsoverlap in the uplink, the transmit power may be insufficient on theterminal side. A solution thereof is to concentrate the transmit poweron the link to one cell by the time division scheme. However, since thedual-registered operation is a technology used in a scenario in whichthere is no information exchange between two systems, sharing of thetime division pattern and the like in two systems will be excluded.Therefore, the terminal itself has to determine on which link thetransmit power of the terminal should be concentrated.

The terminal assigns priority according to the type of data transmittedto both cells. It may assign a higher priority to data transmission thatare important for successfully performing the dual-registered. Forexample, the higher priority is assigned to the random access to thetarget cell, the message associated with the attach operation, and thelike. Alternatively, the higher priority may be alwasys assigned to theuplink data transmission to the target cell. The terminal 6 g-25determines whether or not data transmission to both cells 6 g-05 and 6g-10 overlap each other at each transmission timing, and if overlapped,the transmit power is concentrated on one of the both cells based on thepriority information 6 g-15 and 6 g-20 assigned to each datatransmission. The remaining links may be transmitted with the remainingsmall amount of transmit power, or may restrict the transmission itself.Data that can not be transmitted will be retransmitted at different timeby the retransmission techniques, such as HARQ and ARQ.

FIG. 6H is a diagram illustrating an operation flow block forperforming, by a terminal, an uplink power control according to anembodiment of the present disclosure.

Referring to FIG. 6H, in operation 6 h-05, the terminal assigns priorityaccording to the type of data to be transmitted to one or both of thecells at every transmission timing. In operation 6 h-10, it isdetermined whether the data transmission overlaps due to the generationof the data transmission to both cells is generated. If overlapped, thetransmit power is concentrated on one of the links based on the assignedpriority information in operation 6 h-15. At this time, theconcentration ratio is determined by the terminal implementation. If notoverlapped, in operation 6 h-20, the data to be transmitted at thecorresponding timing is transmitted to the corresponding one cell.

FIG. 6I is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure.

Referring to FIG. 6I, the terminal includes a radio frequency (RF)processor 6 i-10, a baseband processor 6 i-20, a storage 6 i-30, and acontroller 6 i-40.

The RF processor 6 i-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 6 i-10 up-converts a baseband signalprovided from the baseband processor 6 i-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 6 i-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, adigital to analog converter (DAC), an analog to digital converter (ADC),or the like. FIG. 6i illustrates only one antenna but the terminal mayinclude a plurality of antennas. Further, the RF processor 6 i-10 mayinclude a plurality of RF chains. Further, the RF processor 6 i-10 mayperform beamforming. For the beamforming, the RF processor 6 i-10 mayadjust a phase and a size of each of the signals transmitted andreceived through a plurality of antennas or antenna elements. Inaddition, the RF processor may perform MIMO and may receive a pluralityof layers when performing the MIMO operation.

The baseband processor 6 i-20 performs a conversion function between abaseband signal and a bit string according to a physical layer standardof a system. For example, when data are transmitted, the basebandprocessor 6 i-20 generates complex symbols by coding and modulating atransmitted bit string. Further, when data are received, the basebandprocessor 6 i-20 recovers the received bit string by demodulating anddecoding the baseband signal provided from the RF processor 6 i-10. Forexample, according to the OFDM scheme, when data are transmitted, thebaseband processor 6 i-20 generates the complex symbols by coding andmodulating the transmitting bit string, maps the complex symbols tosub-carriers, and then performs an inverse fast Fourier transform (IFFT)operation and a cyclic prefix (CP) insertion to construct the OFDMsymbols. Further, when data are received, the baseband processor 6 i-20divides the baseband signal provided from the RF processor 6 i-10 in anOFDM symbol unit and recovers the signals mapped to the sub-carriers bya fast Fourier transform (FFT) operation and then recovers the receivedbit string by the modulation and decoding.

The baseband processor 6 i-20 and the RF processor 6 i-10 transmit andreceive a signal as described above. Therefore, the baseband processor 6i-20 and the RF processor 6 i-10 may be called a transmitter, areceiver, a transceiver, or a communication unit. Further, at least oneof the baseband processor 6 i-20 and the RF processor 6 i-10 may includea plurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 6 i-20 and the RF processor 6 i-10 may include differentcommunication modules to process signals in different frequency bands.For example, different radio access technologies may include thewireless LAN (for example: IEEE 802.11), a cellular network (forexample: LTE), or the like. Further, different frequency bands mayinclude a super high frequency (SHF) (for example: 2 NRHz) band, amillimeter wave (for example: 60 GHz) band.

The storage 6 i-30 stores data, such as basic programs, applicationprograms, and configuration information for the operation of theterminal. More particularly, the storage 6 i-30 may store informationassociated with a second access node performing wireless communicationusing a second access technology. Further, the storage 6 i-30 providesthe stored data according to the request of the controller 6 i-40.

The controller 6 i-40 includes a multiple connection processor 6 i-42and controls the overall operations of the terminal. For example, thecontroller 6 i-40 transmits and receives a signal through the basebandprocessor 6 i-20 and the RF processor 6 i-10. Further, the controller 6i-40 records and reads data in and from the storage 6 i-40. For thispurpose, the controller 6 i-40 may include at least one processor. Forexample, the controller 6 i-40 may include a communication processor(CP) performing a control for communication and an application processor(AP) controlling an upper layer, such as the application programs.

FIG. 6J is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure.

Referring to FIG. 6J, the base station is configured to include an RFprocessor 6 j-10, a baseband processor 6 j-20, a backhaul communicationunit 6 j-30, a storage 6 j-40, and a controller 6 j-50.

The RF processor 6 j-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 6 j-10 up-converts a baseband signalprovided from the baseband processor 6 j-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 6 j-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC,an ADC, or the like. FIG. 6J illustrates only one antenna but the firstaccess node may include a plurality of antennas. Further, the RFprocessor 6 j-10 may include a plurality of RF chains. Further, the RFprocessor 6 j-10 may perform the beamforming. For the beamforming, theRF processor 6 j-10 may adjust a phase and a size of each of the signalstransmitted/received through a plurality of antennas or antennaelements. The RF processor may perform a downward MIMO operation bytransmitting one or more layers.

The baseband processor 6 j-20 performs a conversion function between thebaseband signal and the bit string according to the physical layerstandard of the first radio access technology. For example, when dataare transmitted, the baseband processor 6 j-20 generates complex symbolsby coding and modulating a transmitted bit string. Further, when dataare received, the baseband processor 2 j-20 recovers the received bitstring by demodulating and decoding the baseband signal provided fromthe RF processor 2 j-10. For example, according to the OFDM scheme, whendata are transmitted, the baseband processor 6 j-20 generates thecomplex symbols by coding and modulating the transmitting bit string,maps the complex symbols to the sub-carriers, and then performs the IFFToperation and the CP insertion to construct the OFDM symbols. Further,when data are received, the baseband processor 6 j-20 divides thebaseband signal provided from the RF processor 6 j-10 in the OFDM symbolunit and recovers the signals mapped to the sub-carriers by the FFToperation and then recovers the receiving bit string by the modulationand decoding. The baseband processor 6 j-20 and the RF processor 6 j-10transmit and receive a signal as described above. Therefore, thebaseband processor 6 j-20 and the RF processor 6 j-10 may be called atransmitter, a receiver, a transceiver, or a communication unit.

The backhaul communication unit 6 j-30 provides an interface forperforming communication with other nodes within the network. Forexample, the backhaul communication unit 6 j-30 converts bit stringstransmitted from the main base station to other nodes, for example, anauxiliary base station, a core network, and the like, into physicalsignals and converts the physical signals received from other nodes intothe bit strings.

The storage 6 j-40 stores data, such as basic programs, applicationprograms, and configuration information for the operation of the mainbase station. More particularly, the storage 6 j-40 may store theinformation on the bearer allocated to the accessed terminal, themeasured results reported from the accessed terminal, and the like.Further, the storage 6 j-40 may store information that is adetermination criterion on whether to provide a multiple connection tothe terminal or stop the multiple connection to the terminal. Further,the storage 6 j-40 provides the stored data according to the request ofthe controller 6 j-50.

The controller 6 j-50 includes a multiple connection processor 6 j-52and controls the general operations of the main base station. Forexample, the controller 6 j-50 transmits/receives a signal through thebaseband processor 6 j-20 and the RF processor 6 j-10 or the backhaulcommunication unit 6 j-30. Further, the controller 6 j-50 records andreads data in and from the storage 6 j-40. For this purpose, thecontroller 6 j-50 may include at least one processor.

Hereinafter, the MAC PDU structures for supporting the next generationmobile communication system is proposed and the method and apparatus forselecting the structures will be described.

Seventh Embodiment

A term used for identifying a connection node used in the followingdescription, a term referring to network entities, a term referring tomessages, a term referring to an interface between network objects, aterm referring to various identification information, or the like areillustrated for convenience of explanation. Accordingly, the presentdisclosure is not limited to terms to be described below and other termsindicating objects having the equivalent technical meaning may be used.

Hereafter, for convenience of explanation, the present disclosure usesterms and names defined in the 3rd generation partnership project longterm evolution (3GPP LTE). However, the present disclosure is notlimited to the terms and names but may also be identically applied tothe system according to other standards.

The RLC apparatus (entity, hereinafter, apparatus) and the PDCPapparatus (entity, hereinafter, apparatus) of the next generation mobilecommunication system may differ from the RLC entity and the PDCP entityof the current LTE system. Therefore, when the next generation mobilecommunication system and the LTE system interwork with each other toprovide a service, the RLC entity and the PDCP entity of the nextgeneration mobile communication system set the correct operation inorder to interwork with the RLC entity and the PDCP entity of the LTEsystem well.

FIG. 7A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure.

Referring to FIG. 7A, a radio access network of an LTE system isconfigured to include next generation base stations (evolved node B,hereinafter, eNB, Node B, or base station) 7 a-05, 7 a-10, 7 a-15, and 7a-20, a mobility management entity (MME) 7 a-25, and a serving-gateway(S-GW) 7 a-30. User equipment (hereinafter, UE or terminal) 7 a-35accesses an external network through the eNBs 7 a-05 to 7 a-20 and theS-GW 7 a-30.

In FIG. 7A, the eNBs 7 a-05 to 7 a-20 correspond to the existing node Bof the UMTS system. The eNB is connected to the UE 7 a-35 through aradio channel and performs more complicated role than the existing nodeB. In the LTE system, in addition to a real-time service like a voiceover Internet protocol (VoIP) through the Internet protocol, all theuser traffics are served through a shared channel and therefore anapparatus for collecting and scheduling status information, such as abuffer status, an available transmission power status, and a channelstate of the terminals is required. Here, the eNBs 7 a-05 to 7 a-20 takecharge of the collecting and scheduling. One eNB generally controls aplurality of cells. For example, to implement a transmission rate of 100Mbps, the LTE system uses, as a radio access technology, OFDM, forexample, in a bandwidth of 20 MHz. Further, an adaptive modulation &coding (hereinafter, called AMC) determining a modulation scheme and achannel coding rate depending on the channel status of the terminal isapplied. The S-GW 7 a-30 is an apparatus for providing a data bearer andgenerates or removes the data bearer according to the control of the MME7 a-25. The MME is an apparatus for performing a mobility managementfunction for the terminal and various control functions and is connectedto a plurality of base stations.

FIG. 7B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure.

Referring to FIG. 7B, the radio protocol of the LTE system is configuredto include PDCPs 7 b-05 and 7 b-40, RLCs 7 b-10 and 7 b-35, and mediumaccess controls (MMCs) 7 b-15 and 7 b-30 in the terminal and the eNB,respectively. The PDCPs 7 b-05 and 7 b-40 are in charge of operations,such as IP header compression/decompression. The main functions of thePDCP are summarized as follows.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUsat PDCP re-establishment procedure for RLC AM)

Reordering function (For split bearers in DC (only support for RLC AM):PDCP PDU routing for transmission and PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs atPDCP re-establishment procedure for RLC AM)

Retransmission function (Retransmission of PDCP SDUs at handover and,for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure,for RLC AM)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink)

The RLCs 7 b-10 and 7 b-35 reconfigures the PDCP PDU to an appropriatesize to perform the ARQ operation or the like. The main functions of theRLC are summarized as follows.

Data transfer function (Transfer of upper layer PDUs)

ARQ function (Error Correction through ARQ (only for AM data transfer))

Concatenation, segmentation, reassembly functions (Concatenation,segmentation and reassembly of RLC SDUs (only for UM and AM datatransfer))

Re-segmentation function (Re-segmentation of RLC data PDUs (only for AMdata transfer))

Reordering function (Reordering of RLC data PDUs (only for UM and AMdata transfer))

Duplicate detection function (Duplicate detection (only for UM and AMdata transfer))

Error detection function (Protocol error detection (only for AM datatransfer))

RLC SDU discard function (RLC SDU discard (only for UM and AM datatransfer))

RLC re-establishment function (RLC re-establishment)

The MACs 7 b-15 and 7 b-30 are connected to several RLC layer apparatusconfigured in one terminal and perform an operation of multiplexing RLCPDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU.The main functions of the MAC are summarized as follows.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MACSDUs belonging to one or different logical channels into/from transportblocks (TB) transferred to/from the physical layer on transportchannels)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

Physical layers 7 b-20 and 7 b-25 perform an operation of channel-codingand modulating higher layer data, making the upper layer data as an OFDMsymbol and transmitting them to a radio channel, or demodulating andchannel-decoding the OFDM symbol received through the radio channel andtransmitting the demodulated and channel-decoded OFDM symbol to theupper layer.

FIG. 7C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure.

Referring to FIG. 7C, a radio access network of a next generation mobilecommunication system (hereinafter referred to as NR or 5G) is configuredto include a next generation base station (New radio node B, hereinafterNR gNB or NR base station) 7 c-10 and a new radio core network (NR CN) 7c-05. The user terminal (new radio user equipment, hereinafter, NR UE orUE) 7 c-15 accesses the external network through the NR gNB 7 c-10 andthe NR CN 7 c-05.

In FIG. 7C, the NR gNB 7 c-10 corresponds to an evolved node B (eNB) ofthe existing LTE system. The NR gNB is connected to the NR UE 7 c-15 viaa radio channel and may provide a service superior to the existing nodeB. In the next generation mobile communication system, since all usertraffics are served through a shared channel, an apparatus forcollecting state information, such as a buffer state, an availabletransmission power state, and a channel state of the terminal to performscheduling is required. The NR NB 7 c-10 may serve as the device. One NRgNB generally controls a plurality of cells. In order to realizehigh-speed data transmission compared with the current LTE, the NR gNBmay have an existing maximum bandwidth or more, and may be additionallyincorporated into a beam-forming technology may be applied by using OFDMas a radio access technology 7 c-20. Further, an adaptive modulation &coding (hereinafter, called AMC) determining a modulation scheme and achannel coding rate depending on the channel status of the terminal isapplied. The NR CN 7 c-05 may perform functions, such as mobilitysupport, bearer setup, QoS setup, and the like. The NR CN is a devicefor performing a mobility management function for the terminal andvarious control functions and is connected to a plurality of basestations. In addition, the next generation mobile communication systemcan interwork with the existing LTE system, and the NR CN is connectedto the MME 7 c-25 through the network interface. The MME is connected tothe eNB 7 c-30 which is the existing base station.

FIG. 7D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 7D, the radio protocol of the next generation mobilecommunication system is configured to include NR PDCPs 7 d-05 and 7d-40, NR RLCs 7 d-10 and 7 d-35, and NR MACs 7 d-15 and 7 d-30 in theterminal and the NR base station. The main functions of the NR PDCPs 7d-05 and 7 d-40 may include some of the following functions.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Reordering function (PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs)

Retransmission function (Retransmission of PDCP SDUs)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink))

In this case, the reordering function of the NR PDCP apparatus refers toa function of rearranging PDCP PDUs received in a lower layer in orderbased on a PDCP sequence number (SN) and may include a function oftransferring data to an upper layer in the rearranged order, a functionof recording PDCP PDUs lost by the reordering, a function of reporting astate of the lost PDCP PDUs to a transmitting side, and a function ofrequesting a retransmission of the lost PDCP PDUs.

The main functions of the NR RLCs 7 d-10 and 7 d-35 may include some ofthe following functions.

Data transfer function (Transfer of upper layer PDUs)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Out-of-sequence delivery function (Out-of-sequence delivery of upperlayer PDUs)

ARQ function (Error correction through HARQ)

Concatenation, segmentation, reassembly function (Concatenation,segmentation and reassembly of RLC SDUs)

Re-segmentation function (Re-segmentation of RLC data PDUs)

Reordering function (Reordering of RLC data PDUs)

Duplicate detection function (Duplicate detection)

Error detection function (Protocol error detection)

RLC SDU discard function (RLC SDU discard)

RLC re-establishment function (RLC re-establishment)

In the above description, the in-sequence delivery function of the NRRLC apparatus refers to a function of delivering RLC SDUs received froma lower layer to an upper layer in order, and may include a function ofreassembling and transferring an original one RLC SDU which is dividedinto a plurality of RLC SDUs and received, a function of rearranging thereceived RLC PDUs based on the RLC sequence number (SN) or the PDCPsequence number (SN), a function of recording the RLC PDUs lost by thereordering, a function of reporting a state of the lost RLC PDUs to thetransmitting side, a function of requesting a retransmission of the lostRLC PDUs, a function of transferring only the SLC SDUs before the lostRLC SDU to the upper layer in order when there is the lost RLC SDU, afunction of transferring all the received RLC SDUs to the upper layerbefore a predetermined timer starts if the timer expires even if thereis the lost RLC SDU, or a function of transferring all the RLC SDUsreceived until now to the upper layer in order if the predeterminedtimer expires even if there is the lost RLC SDU.

In this case, the out-of-sequence delivery function of the NR RLCapparatus refers to a function of directly delivering the RLC SDUsreceived from the lower layer to the upper layer regardless of order,and may include a function of reassembling and transferring an originalone RLC SDU which is divided into several RLC SDUs and received, and afunction of storing the RLC SN or the PDCP SP of the received RLC PDUsand arranging it in order to record the lost RLC PDUs.

The NR MACs 2 d-15 and 3 d-30 may be connected to several NR RLC layerapparatus configured in one terminal, and the main functions of the NRMAC may include some of the following functions.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing and demultiplexing function (Multiplexing/demultiplexing ofMAC SDUs)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

The NR PHY layers 7 d-20 and 7 d-25 may perform an operation ofchannel-coding and modulating higher layer data, making the upper layerdata as an OFDM symbol and transmitting them to a radio channel, ordemodulating and channel-decoding the OFDM symbol received through theradio channel and transmitting the demodulated and channel-decoded OFDMsymbol to the upper layer.

FIG. 7E is a diagram illustrating a procedure of setting, by a terminal,apparatuses (entity, hereinafter, apparatus) of each layer in a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 7E, a procedure is illustrated of setting a connectionwith a network via which a terminal transmits/receives data and settingapparatuses (entity, hereinafter, apparatuses) of each layer.

If there is data to be transmitted, a terminal 7 e-01 (hereinafter,referred to as an idle mode UE) for which no connection is currentlyestablished performs an RRC connection establishment procedure with theLTE base station or the NR base station 7 e-02. The terminal establishesuplink transmission synchronization with the base station through arandom access procedure and transmits an RRCConnectionRequest message tothe base station (7 e-05). The message includes an identifier of theterminal and a cause for setting up a connection. The base stationtransmits an RRCConnectionSetup message to allow the terminal to set theRRC connection (7 e-10). The message may store RRC connectionconfiguration information, configuration information of each layer, andthe like. In other words, it may include configuration information onthe PHY or NR PHY apparatus, the MAC or NR MAC apparatus, the RLC or NRRLC apparatus, the PDCP or the NR PDCP apparatus, and the informationinstructing the setting for the specific functions among the functions(functions for each layer described in FIG. 7B or 7D) supported by thelayer apparatuses. The RRC connection is also called a signaling radiobearer (SRB) and is used for transmission and reception of the RRCmessage that is a control message between the terminal and the basestation. The terminal establishing the RRC connection transmits anRRCConnetionSetupComplete message to the base station (7 e-15). The basestation transmits an RRCConnectionReconfiguration message to theterminal in order to set up a data radio bearer (DRB) (7 e-20). Theconfiguration information of each layer and the like may be stored inthe message. In other words, it may include configuration information onthe PHY or NR PHY apparatus, the MAC or NR MAC apparatus, the RLC or NRRLC apparatus, the PDCP or the NR PDCP apparatus, and the informationinstructing the setting for the specific functions among the functions(functions for each layer described in FIG. 7B or 7D) supported by thelayer apparatuses. In addition, the message includes the configurationinformation of the DRB in which user data are processed, and theterminal applies the information to set the DRB and set the functions ofeach layer and transmits an RRCConnectionReconfigurationComplete messageto the base station (7 e-25). If the above procedure is completed, theterminal transmits and receives data to and from the base station (7e-30). While transmitting and receiving data, the base station may againtransmit the RRCConnectionReconfiguration message to the terminal (7e-35), if necessary, and again set the configuration information of eachlayer of the terminal. In other words, it may include configurationinformation on the PHY or NR PHY apparatus, the MAC or NR MAC apparatus,the RLC or NR RLC apparatus, the PDCP or the NR PDCP apparatus, and theinformation instructing the setting for the specific functions among thefunctions (functions for each layer described in FIG. 7B or 7D)supported by the layer apparatuses. In addition, the message may includethe information for setting the interworking between the LTE basestation and the NR base station. The information for setting theinterworking between the LTE base station and the NR base station mayinclude information indicating a 3C type or a 7a type, information oneach layer device according to each type, and the like. Upon completionof the setting of apparatuses of each layer according to the message,the terminal transmits an RRCConnectionReconfigurationComplete messageto the base station (7 e-40).

FIG. 7F is a diagram illustrating scenarios which allow a terminal toreceive services through an LTE base station and an NR base station in anext generation mobile communication system according to an embodimentof the present disclosure.

Referring to FIG. 7F, 7 f-01 represents a scenario in which the LTE basestation is a master in 3C type interworking of the LTE base station andthe NR base station, 7 f-02 represents a scenario in which the NR basestation is the master in the 3C type interworking between the LTE basestation and the NR base station, 7 f-03 represents a 7a-typeinterworking scenario of the LTE base station and the NR base station,and 7 f-04 represents a scenario in which a service is received onlyfrom the NR base station.

In a 7-1-th embodiment of the present disclosure, the NR RLC operationof the terminal is set as follows.

If the terminal receives an RRC control message (RRCConnectionSetupmessage 7 e-10 or RRCConnectionReconfiguration message 7 e-20, 7 e-35 inFIG. 7E) for instructing the NR RLC apparatus setup for a predeterminedradio bearer from the base station, the terminal confirms theinformation of the message, generates the NR RLC apparatus, is connectedto the PDCP apparatus or the NR PDCP apparatus and the NR MAC apparatus,and receives data through the NR RLC apparatus, processes the data, andtransfers the processed data to the upper layer apparatus (PDCP or NRPDCP apparatus). The method by which the NR RLC apparatus processes thedata in the above procedure is as follows according to predeterminedconditions.

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the second method is applied toprocess the data

The first condition refers to the case where the NR RLC apparatus isconnected to the LTE PDCP apparatus and the NR MAC apparatus (7 f-15 of7 f-01) or the case where a control message for setting up the NR RLCapparatus is received via the LTE.

The second condition refers to the case where the NR RLC apparatus isconnected to the NR PDCP apparatus and the NR MAC apparatus (7 f-25 of 7f-02, 7 f-35 of 7 f-03, 7 f-45 of 7 f-04) or the case where the controlmessage for setting up the NR RLC apparatus is received via the NR.

The first method is to reassemble the received RLC PDU into an RLC SDUand transmit it to the PDCP apparatus if the predetermined condition issatisfied. For example, the in-sequence delivery function is set. Thepredetermined condition refers to the case where a predetermined timeelapses after there is no non-received RLC PDU or a non-received RLC PDUis generated. In the above description, the in-sequence deliveryfunction of the NR RLC apparatus refers to a function of delivering RLCSDUs received from a lower layer to a higher layer in order, and mayinclude a function of reassembling and transferring an original one RLCSDU which is divided into a plurality of RLC SDUs and received, afunction of rearranging the received RLC PDUs based on the RLC sequencenumber (SN) or the PDCP sequence number (SN), a function of recordingthe RLC PDUs lost by the reordering, a function of reporting a state ofthe lost RLC PDUs to the transmitting side, a function of requesting aretransmission of the lost RLC PDUs, a function of transferring only theSLC SDUs before the lost RLC SDU to the higher layer in order when thereis the lost RLC SDU, a function of transferring all the received RLCSDUs to the higher layer before a predetermined timer starts if thetimer expires even if there is the lost RLC SDU, or a function oftransferring all the RLC SDUs received until now to the higher layer inorder if the predetermined timer expires even if there is the lost RLCSDU.

If the RLC SDU may be reassembled in the received RLC PDU, the secondmethod immediately reassembles the RLC SDU and transfers the reassembledRLC SDU to the PDCP apparatus. For example, the out-of-sequence deliveryfunction is set. In this case, the out-of-sequence delivery function ofthe NR RLC apparatus refers to a function of directly delivering the RLCSDUs received from the lower layer to the higher layer regardless oforder, and may include a function of reassembling and transferring anoriginal one RLC SDU which is divided into several RLC SDUs andreceived, and a function of storing the RLC SN or the PDCP SP of thereceived RLC PDUs and arranging it in order to record the lost RLC PDUs.

The operation of the terminal in a 7-1-th embodiment of the presentdisclosure is the same as FIG. 7H. The terminal confirms the firstcondition or the second condition in operation 7 h-05, and if the firstcondition is satisfied, proceeds to operation 7 h-10 to process data bythe first method and if the second condition is satisfied, proceeds tooperation 7 h-15 to process data by the second method.

In a 7-2-th embodiment of the present disclosure, the NR RLC operationof the terminal is set as follows.

If the terminal receives an RRC control message (RRCConnectionSetupmessage 7 e-10 or RRCConnectionReconfiguration message 7 e-20, 7 e-35 inFIG. 7E) for instructing the NR RLC apparatus setup for a predeterminedradio bearer from the base station, the terminal confirms theinformation of the message, generates the NR RLC apparatus, is connectedto the NR PDCP apparatus and the NR MAC apparatus, receives data throughthe NR RLC apparatus, processes the data, and transfer the processeddata to the upper layer apparatus (NR PDCP apparatus) (7 f-45 of 7f-04). The method by which the NR RLC apparatus processes the data inthe above procedure is as follows according to predetermined conditions.

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the second method is applied toprocess the data

The first condition is the case where the NR RLC apparatus is set in theSRB in the AM mode.

The second condition is the case where the NR RLC apparatus is set inthe DRB in the AM mode.

The first method is to reassemble the received RLC PDU into an RLC SDUand transmit it to the PDCP apparatus if the predetermined condition issatisfied. For example, the in-sequence delivery function is set. Thepredetermined condition refers to the case where a predetermined timeelapses after there is no non-received RLC PDU or a non-received RLC PDUis generated. In the above description, the in-sequence deliveryfunction of the NR RLC apparatus refers to a function of delivering RLCSDUs received from a lower layer to a higher layer in order, and mayinclude a function of reassembling and transferring an original one RLCSDU which is divided into a plurality of RLC SDUs and received, afunction of rearranging the received RLC PDUs based on the RLC sequencenumber (SN) or the PDCP sequence number (SN), a function of recordingthe RLC PDUs lost by the reordering, a function of reporting a state ofthe lost RLC PDUs to the transmitting side, a function of requesting aretransmission of the lost RLC PDUs, a function of transferring only theSLC SDUs before the lost RLC SDU to the higher layer in order when thereis the lost RLC SDU, a function of transferring all the received RLCSDUs to the higher layer before a predetermined timer starts if thetimer expires even if there is the lost RLC SDU, or a function oftransferring all the RLC SDUs received until now to the higher layer inorder if the predetermined timer expires even if there is the lost RLCSDU.

If the RLC SDU may be reassembled in the received RLC PDU, the secondmethod immediately reassembles the RLC SDU and transfers the reassembledRLC SDU to the PDCP apparatus. For example, the out-of-sequence deliveryfunction is set. In this case, the out-of-sequence delivery function ofthe NR RLC apparatus refers to a function of directly delivering the RLCSDUs received from the lower layer to the higher layer regardless oforder, and may include a function of reassembling and transferring anoriginal one RLC SDU which is divided into several RLC SDUs andreceived, and a function of storing the RLC SN or the PDCP SP of thereceived RLC PDUs and arranging it in order to record the lost RLC PDUs.

The operation of the terminal in a 7-2-th embodiment of the presentdisclosure is the same as FIG. 7H. The terminal confirms the firstcondition or the second condition in operation 7 h-05, and if the firstcondition is satisfied, proceeds to operation 7 h-10 to process data bythe first method and if the second condition is satisfied, proceeds tooperation 7 h-15 to process data by the second method.

In a 7-3-th embodiment of the present disclosure, the NR RLC operationof the terminal is set as follows.

If the terminal receives an RRC control message (RRCConnectionSetupmessage 7 e-10 or RRCConnectionReconfiguration message 7 e-20, 7 e-35 inFIG. 7E) for instructing the NR RLC apparatus setup for a predeterminedradio bearer from the base station, the terminal confirms theinformation of the message, generates the NR RLC apparatus, connectsbetween the NR PDCP apparatus and the NR MAC apparatus, and receivesdata through the NR RLC apparatus, processes the data, and transfers theprocessed data to the upper layer apparatus (NR PDCP apparatus) (7 f-45of 7 f-04). The method by which the NR RLC apparatus processes the datain the above procedure is as follows according to predeterminedconditions.

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the second method is applied toprocess the data

The first condition is the case where the NR RLC apparatus is set in theSRB in the AM mode, the case where the NR RLC apparatus is set in theDRB in the AM mode and receives the information indicating that thefirst method should be applied from the RRC control message, or the casewhere the NR RLC apparatus is set in the UM mode.

The second condition is the case where the NR RLC apparatus is set tothe DRB in the AM mode and does not receive the information indicatingthat the first method should be applied from the control message orreceives the information indicating that the first method should beapplied from the control message.

The first method is to reassemble the received RLC PDU into an RLC SDUand transmit it to the PDCP apparatus if the predetermined condition issatisfied. For example, the in-sequence delivery function is set. Thepredetermined condition refers to the case where a predetermined timeelapses after there is no non-received RLC PDU or a non-received RLC PDUis generated. In the above description, the in-sequence deliveryfunction of the NR RLC apparatus refers to a function of delivering RLCSDUs received from a lower layer to a higher layer in order, and mayinclude a function of reassembling and transferring an original one RLCSDU which is divided into a plurality of RLC SDUs and received, afunction of rearranging the received RLC PDUs based on the RLC sequencenumber (SN) or the PDCP sequence number (SN), a function of recordingthe RLC PDUs lost by the reordering, a function of reporting a state ofthe lost RLC PDUs to the transmitting side, a function of requesting aretransmission of the lost RLC PDUs, a function of transferring only theSLC SDUs before the lost RLC SDU to the higher layer in order when thereis the lost RLC SDU, a function of transferring all the received RLCSDUs to the higher layer before a predetermined timer starts if thetimer expires even if there is the lost RLC SDU, or a function oftransferring all the RLC SDUs received until now to the higher layer inorder if the predetermined timer expires even if there is the lost RLCSDU.

If the RLC SDU may be reassembled in the received RLC PDU, the secondmethod immediately reassembles the RLC SDU and transfers the reassembledRLC SDU to the PDCP apparatus. For example, the out-of-sequence deliveryfunction is set. In this case, the out-of-sequence delivery function ofthe NR RLC apparatus refers to a function of directly delivering the RLCSDUs received from the lower layer to the higher layer regardless oforder, and may include a function of reassembling and transferring anoriginal one RLC SDU which is divided into several RLC SDUs andreceived, and a function of storing the RLC SN or the PDCP SP of thereceived RLC PDUs and arranging it in order to record the lost RLC PDUs.

The operation of the terminal in a 7-3-th embodiment of the presentdisclosure is the same as FIG. 7H. The terminal confirms the firstcondition or the second condition in operation 7 h-05, and if the firstcondition is satisfied, proceeds to operation 7 h-10 to process data bythe first method and if the second condition is satisfied, proceeds tooperation 7 h-15 to process data by the second method.

In a 7-4-th embodiment of the present disclosure, the NR RLC operationof the NR base station is set as follows.

The NR base station sets the NR RLC apparatus for a predetermined radiobearer. The NR base station generates the NR RLC apparatus, is connectedto the PDCP apparatus, the NR PDCP apparatus and the NR MAC apparatus,receives data through the NR RLC apparatus, processes the data, andtransfers the processed data to the upper layer apparatus (PDCP or NRPDCP apparatus). The method by which the NR RLC apparatus processes thedata in the above procedure is as follows according to predeterminedconditions.

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the second method is applied toprocess the data

The first condition refers to the case where the NR RLC apparatus isconnected to the LTE PDCP apparatus and the NR MAC apparatus (7 f-10 of7 f-01) or the case where a control message for setting up the NR RLCapparatus is received via the LTE.

The second condition refers to the case where the NR RLC apparatus isconnected to the NR PDCP apparatus and the NR MAC apparatus (7 f-20 of 7f-02, 7 f-30 of 7 f-03, 7 f-40 of 7 f-04) or the case where the controlmessage for setting up the NR RLC apparatus is received via the NR.

The first method is to reassemble the received RLC PDU into an RLC SDUand transmit it to the PDCP apparatus if the predetermined condition issatisfied. For example, the in-sequence delivery function is set. Thepredetermined condition refers to the case where a predetermined timeelapses after there is no non-received RLC PDU or a non-received RLC PDUis generated. In the above description, the in-sequence deliveryfunction of the NR RLC apparatus refers to a function of delivering RLCSDUs received from a lower layer to a higher layer in order, and mayinclude a function of reassembling and transferring an original one RLCSDU which is divided into a plurality of RLC SDUs and received, afunction of rearranging the received RLC PDUs based on the RLC sequencenumber (SN) or the PDCP sequence number (SN), a function of recordingthe RLC PDUs lost by the reordering, a function of reporting a state ofthe lost RLC PDUs to the transmitting side, a function of requesting aretransmission of the lost RLC PDUs, a function of transferring only theSLC SDUs before the lost RLC SDU to the higher layer in order when thereis the lost RLC SDU, a function of transferring all the received RLCSDUs to the higher layer before a predetermined timer starts if thetimer expires even if there is the lost RLC SDU, or a function oftransferring all the RLC SDUs received until now to the higher layer inorder if the predetermined timer expires even if there is the lost RLCSDU.

If the RLC SDU may be reassembled in the received RLC PDU, the secondmethod immediately reassembles the RLC SDU and transfers the reassembledRLC SDU to the PDCP apparatus. For example, the out-of-sequence deliveryfunction is set. In this case, the out-of-sequence delivery function ofthe NR RLC apparatus refers to a function of directly delivering the RLCSDUs received from the lower layer to the higher layer regardless oforder, and may include a function of reassembling and transferring anoriginal one RLC SDU which is divided into several RLC SDUs andreceived, and a function of storing the RLC SN or the PDCP SP of thereceived RLC PDUs and arranging it in order to record the lost RLC PDUs.

FIG. 7I is a diagram illustrating an operation of a base stationaccording to 7-4-th, 7-5-th, 7-6-th, and 7-8-th embodiments of thepresent disclosure.

Referring to FIG. 7I, the terminal confirms the first condition or thesecond condition in operation 7 i-05, and if the first condition issatisfied, proceeds to operation 7 i-10 to process data by the firstmethod and if the second condition is satisfied, proceeds to operation 7i-15 to process data by the second method.

In a 7-5-th embodiment of the present disclosure, the NR RLC operationof the NR base station is set as follows.

The NR base station sets the NR RLC apparatus for a predetermined radiobearer. The NR base station generates the NR RLC apparatus, is connectedto the NR PDCP apparatus and the NR MAC apparatus, receives data throughthe NR RLC apparatus, processes the data, and transmits the processeddata to the upper layer apparatus (NR PDCP apparatus) (7 f-40 of 7f-04). The method by which the NR RLC apparatus processes the data inthe above procedure is as follows according to predetermined conditions.

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the second method is applied toprocess the data

The first condition is the case where the NR RLC apparatus is set in theSRB in the AM mode.

The second condition is the case where the NR RLC apparatus is set inthe DRB in the AM mode.

The first method is to reassemble the received RLC PDU into an RLC SDUand transmit it to the PDCP apparatus if the predetermined condition issatisfied. For example, the in-sequence delivery function is set. Thepredetermined condition refers to the case where a predetermined timeelapses after there is no non-received RLC PDU or a non-received RLC PDUis generated. In the above description, the in-sequence deliveryfunction of the NR RLC apparatus refers to a function of delivering RLCSDUs received from a lower layer to a higher layer in order, and mayinclude a function of reassembling and transferring an original one RLCSDU which is divided into a plurality of RLC SDUs and received, afunction of rearranging the received RLC PDUs based on the RLC sequencenumber (SN) or the PDCP sequence number (SN), a function of recordingthe RLC PDUs lost by the reordering, a function of reporting a state ofthe lost RLC PDUs to the transmitting side, a function of requesting aretransmission of the lost RLC PDUs, a function of transferring only theSLC SDUs before the lost RLC SDU to the higher layer in order when thereis the lost RLC SDU, a function of transferring all the received RLCSDUs to the higher layer before a predetermined timer starts if thetimer expires even if there is the lost RLC SDU, or a function oftransferring all the RLC SDUs received until now to the higher layer inorder if the predetermined timer expires even if there is the lost RLCSDU.

If the RLC SDU may be reassembled in the received RLC PDU, the secondmethod immediately reassembles the RLC SDU and transfers the reassembledRLC SDU to the PDCP apparatus. For example, the out-of-sequence deliveryfunction is set. In this case, the out-of-sequence delivery function ofthe NR RLC apparatus refers to a function of directly delivering the RLCSDUs received from the lower layer to the higher layer regardless oforder, and may include a function of reassembling and transferring anoriginal one RLC SDU which is divided into several RLC SDUs andreceived, and a function of storing the RLC SN or the PDCP SP of thereceived RLC PDUs and arranging it in order to record the lost RLC PDUs.

The operation of the base station in a 7-5-th embodiment of the presentdisclosure is the same as FIG. 7I. The terminal confirms the firstcondition or the second condition in operation 7 i-05, and if the firstcondition is satisfied, proceeds to operation 7 i-10 to process data bythe first method and if the second condition is satisfied, proceeds tooperation 7 i-15 to process data by the second method.

In a 7-6-th embodiment of the present disclosure, the NR RLC operationof the NR base station is set as follows.

The NR base station sets the NR RLC apparatus for a predetermined radiobearer. The NR base station generates the NR RLC apparatus, is connectedto the NR PDCP apparatus and the NR MAC apparatus, receives data throughthe NR RLC apparatus, processes the data, and transmits the processeddata to the upper layer apparatus (NR PDCP apparatus) (7 f-40 of 7f-04). The method by which the NR RLC apparatus processes the data inthe above procedure is as follows according to predetermined conditions.

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the second method is applied toprocess the data

The first condition is the case where the NR RLC apparatus is set in theSRB in the AM mode, the case where the NR RLC apparatus is set in theDRB in the AM mode and receives the information indicating that thefirst method should be applied from the RRC control message, or the casewhere the NR RLC apparatus is set in the UM mode.

The second condition is the case where the NR RLC apparatus is set tothe DRB in the AM mode and does not receive the information indicatingthat the first method should be applied from the control message orreceives the information indicating that the first method should beapplied from the control message.

The first method is to reassemble the received RLC PDU into an RLC SDUand transmit it to the PDCP apparatus if the predetermined condition issatisfied. For example, the in-sequence delivery function is set. Thepredetermined condition refers to the case where a predetermined timeelapses after there is no non-received RLC PDU or a non-received RLC PDUis generated. In the above description, the in-sequence deliveryfunction of the NR RLC apparatus refers to a function of delivering RLCSDUs received from a lower layer to a higher layer in order, and mayinclude a function of reassembling and transferring an original one RLCSDU which is divided into a plurality of RLC SDUs and received, afunction of rearranging the received RLC PDUs based on the RLC sequencenumber (SN) or the PDCP sequence number (SN), a function of recordingthe RLC PDUs lost by the reordering, a function of reporting a state ofthe lost RLC PDUs to the transmitting side, a function of requesting aretransmission of the lost RLC PDUs, a function of transferring only theSLC SDUs before the lost RLC SDU to the higher layer in order when thereis the lost RLC SDU, a function of transferring all the received RLCSDUs to the higher layer before a predetermined timer starts if thetimer expires even if there is the lost RLC SDU, or a function oftransferring all the RLC SDUs received until now to the higher layer inorder if the predetermined timer expires even if there is the lost RLCSDU.

If the RLC SDU may be reassembled in the received RLC PDU, the secondmethod immediately reassembles the RLC SDU and transfers the reassembledRLC SDU to the PDCP apparatus. For example, the out-of-sequence deliveryfunction is set. In this case, the out-of-sequence delivery function ofthe NR RLC apparatus refers to a function of directly delivering the RLCSDUs received from the lower layer to the higher layer regardless oforder, and may include a function of reassembling and transferring anoriginal one RLC SDU which is divided into several RLC SDUs andreceived, and a function of storing the RLC SN or the PDCP SP of thereceived RLC PDUs and arranging it in order to record the lost RLC PDUs.

The operation of the base station in a 7-4-th embodiment of the presentdisclosure is the same as FIG. 7I. The terminal confirms the firstcondition or the second condition in operation 7 i-05, and if the firstcondition is satisfied, proceeds to operation 7 i-10 to process data bythe first method and if the second condition is satisfied, proceeds tooperation 7 i-15 to process data by the second method.

FIG. 7G is a diagram illustrating a scenario which allows a terminal toreceive services through an LTE base station and an NR base station in anext generation mobile communication system according to an embodimentof the present disclosure.

Referring to FIG. 7G, 7 g-01 represents a split bearer scenario in whichthe NR base station is a master and data is transmitted through NRbearer and LTE bearer in 3C type interworking between the LTE basestation and NR base station, 7 g-02 represents a scenario in which theNR base station is a master and data is transmitted only through the LTEbearer in the in the 3C type interworking between the LTE base stationand NR base station, 7 g-03 represents a 7a-type interworking scenarioof the LTE base station and the NR base station, and 7 g-04 represents ascenario in which the service is received only from the NR base station.

In a 7-7-th embodiment of the present disclosure, the NR PDCP operationof the terminal is set as follows.

If the terminal receives an RRC control message (RRCConnectionSetupmessage 7 e-10 or RRCConnectionReconfiguration message 7 e-20, 7 e-35 inFIG. 7E) for instructing the NR PDCP apparatus setup for a predeterminedradio bearer from the base station, the terminal confirms theinformation of the message, generates the NR PDCP apparatus, isconnected to the NR PDCP apparatus, and receives data through the NRPDCP apparatus, processes the data, and transfers the processed data tothe upper layer apparatus (network layer or apparatus). The method bywhich the NR PDCP apparatus processes the data in the above procedure isas follows according to predetermined conditions.

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the second method is applied toprocess the data.

The first condition is the case where the NR PDCP apparatus is connectedto the NR RLC apparatus and the LTE RLC apparatus and data is set to bereceived through the NR RLC apparatus and the LTE RLC apparatus, thecase where the control message setting the NR PDCP apparatus is receivedthrough the NR and data is set to be received through the NR RLCapparatus and the LTE RLC apparatus (7 g-15 of 7 g-01), the case wherethe NR PDCP apparatus is connected only to the NR RLC apparatus, or thecase where the NR PDCP apparatus is not connected to the LTE basestation but is connected to only the NR base station (7 g-35 of 7 g-03,7 g-45 of 7 g-04).

The second condition is the case where the NR PDCP apparatus isconnected to the NR RLC and the LTE RLC and data is set to be receivedonly by the LTE RLC apparatus (7 g-25 of 7 g-02), or where the controlmessage for setting the NR PDCP apparatus is received through the NR anddata is set to be received only by the LTE RLC apparatus.

In the first method, if the predetermined condition is satisfied, the NRPDCP apparatus performs the predetermined processing on the receivedPDCP PDUs and transfers the processed PDCP PDUs to the upper layer orthe apparatus. For example, the reordering function is set. Thepredetermined condition is the case where a predetermined time haselapsed after a non-received PDCP PDU does not exist or a non-receivedPDCP PDU is generated. The predetermined processing may includeoperations of removing the PDCP header from the PDCP PDU, decrypting it,verifying the integrity thereof if necessary, and decompressing theheader of the packet. In this case, the reordering function of the NRPDCP apparatus refers to a function of rearranging PDCP PDUs received ina lower layer in order based on a PDCP sequence number (SN) and mayinclude a function of transferring data to a higher layer in therearranged order, a function of recording PDCP PDUs lost by thereordering, a function of reporting a state of the lost PDCP PDUs to atransmitting side, and a function of requesting a retransmission of thelost PDCP PDUs.

The second method performs the predetermined processing on the receivedPDCP PDUs and transfers the processed PDCP PDUs to the upper layer orthe apparatus. The predetermined processing may include the operationsof removing the PDCP header from the PDCP PDU, decrypting it, verifyingthe integrity thereof if necessary, and decompressing the header of thepacket. The process may be understood as the process in which the NRPDCP apparatus performs predetermined processing on the PDCP PDUs andthen transmits the processed PDCP PDUs to the upper layer or apparatuswithout setting the reordering function, or may be understood theprocess in which the NR PDCP apparatus performs predetermined processingon the PDCP PDUs and immediately transmits the processed PDCP PDUs tothe upper layer or apparatus.

FIG. 7H is a diagram illustrating an operation of a terminal accordingto 7-1-th, 7-2-th, 7-3-th, and 7-7-th embodiments of the presentdisclosure.

Referring to FIG. 7H, the terminal confirms the first condition or thesecond condition in operation 7 h-05, and if the first condition issatisfied, proceeds to operation 7 h-10 to process data by the firstmethod and if the second condition is satisfied, proceeds to operation 7h-15 to process data by the second method.

In a 7-8-th embodiment of the present disclosure, the NR PDCP operationof the NR base station is set as follows.

The NR base station sets the NR PDCP apparatus for a predetermined radiobearer. For example, the NR PDCP apparatus is generated and connected tothe NR RLC apparatus, receives data through the NR PDCP apparatus,processes the data, and transmits the processed data to the upper layerapparatus (network layer or apparatus). The method by which the NR PDCPapparatus processes the data in the above procedure is as followsaccording to predetermined conditions.

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the second method is applied toprocess the data

The first condition is the case where the NR PDCP apparatus is connectedto the NR RLC apparatus and the LTE RLC apparatus and data is set to bereceived through the NR RLC apparatus and the LTE RLC apparatus, thecase where the NR base station itself determines the setting of the NRPDCP apparatus is received through the NR and data is set to be receivedthrough the NR RLC apparatus and the LTE RLC apparatus (7 g-10 of 7g-01), the case where the NR PDCP apparatus is connected only to the NRRLC apparatus, or the case where the NR PDCP apparatus is not connectedto the LTE base station but is connected to only the NR base station (7g-30 of 7 g-03, 7 g-40 of 7 g-04).

The second condition is the case where the NR PDCP apparatus isconnected to the NR RLC and the LTE RLC and data is set to betransmitted to only by the LTE RLC apparatus, or where the NR basestation itself determines the setting of the NR PDCP apparatus and thedata is set to be received only by the LTE RLC apparatus (7 g-20 of 7g-02).

In the first method, if the predetermined condition is satisfied, the NRPDCP apparatus performs the predetermined processing on the receivedPDCP PDUs and transfers the processed PDCP PDUs to the upper layer orthe apparatus. For example, the reordering function is set. Thepredetermined condition is the case where a predetermined time haselapsed after a non-received PDCP PDU does not exist or a non-receivedPDCP PDU is generated. The predetermined processing may includeoperations of removing the PDCP header from the PDCP PDU, decrypting it,verifying the integrity thereof if necessary, and decompressing theheader of the packet. In this case, the reordering function of the NRPDCP apparatus refers to a function of rearranging PDCP PDUs received ina lower layer in order based on a PDCP sequence number (SN) and mayinclude a function of transferring data to a higher layer in therearranged order, a function of recording PDCP PDUs lost by thereordering, a function of reporting a state of the lost PDCP PDUs to atransmitting side, and a function of requesting a retransmission of thelost PDCP PDUs.

The second method performs the predetermined processing on the receivedPDCP PDUs and transfers the processed PDCP PDUs to the upper layer orthe apparatus. The predetermined processing may include the operationsof removing the PDCP header from the PDCP PDU, decrypting it, verifyingthe integrity thereof if necessary, and decompressing the header of thepacket.

FIG. 7J is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure.

Referring to FIG. 7J, the terminal includes a radio frequency (RF)processor 7 j-10, a baseband processor 7 j-20, a storage 7 j-30, and acontroller 7 j-40.

The RF processor 7 j-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 1 j-10 up-converts a baseband signalprovided from the baseband processor 1 j-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 7 j-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, adigital to analog converter (DAC), an analog to digital converter (ADC),or the like. FIG. 4H illustrates only one antenna but the terminal mayinclude a plurality of antennas. Further, the RF processor 7 j-10 mayinclude a plurality of RF chains. Further, the RF processor 7 j-10 mayperform beamforming. For the beamforming, the RF processor 7 j-10 mayadjust a phase and a size of each of the signals transmitted andreceived through a plurality of antennas or antenna elements. Inaddition, the RF processor may perform MIMO and may receive a pluralityof layers when performing a MIMO operation. The RF processor 7 j-10 mayperform reception beam sweeping by appropriately configuring a pluralityof antennas or antenna elements under the control of the controller oradjust a direction and a beam width of the reception beam so that thereception beam is resonated with the transmission beam.

The baseband processor 7 j-20 performs a conversion function between abaseband signal and a bit string according to a physical layer standardof a system. For example, when data are transmitted, the basebandprocessor 7 j-20 generates complex symbols by coding and modulating atransmitted bit string. Further, when data are received, the basebandprocessor 1 j-20 recovers the received bit string by demodulating anddecoding the baseband signal provided from the RF processor 1 j-10. Forexample, according to the OFDM scheme, when data are transmitted, thebaseband processor 7 j-20 generates the complex symbols by coding andmodulating the transmitting bit string, maps the complex symbols tosub-carriers, and then performs an inverse fast Fourier transform (IFFT)operation and a cyclic prefix (CP) insertion to configure the OFDMsymbols. Further, when data are received, the baseband processor 7 j-20divides the baseband signal provided from the RF processor 7 j-10 in anOFDM symbol unit and recovers the signals mapped to the sub-carriers bya fast Fourier transform (FFT) operation and then recovers the receivedbit string by the modulation and decoding.

The baseband processor 1 j-20 and the RF processor 1 j-10 transmit andreceive a signal as described above. Therefore, the baseband processor 7j-20 and the RF processor 7 j-10 may be called a transmitter, areceiver, a transceiver, or a communication unit. Further, at least oneof the baseband processor 1 j-20 and the RF processor 1 j-10 may includea plurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 7 j-20 and the RF processor 7 j-10 may include differentcommunication modules to process signals in different frequency bands.For example, the different wireless access technologies may include anLTE network, an NR network, and the like. Further, different frequencybands may include a super high frequency (SHF) (for example: 2.5 GHz, 5GHz) band, a millimeter wave (for example: 60 GHz) band.

The storage 7 j-30 stores data, such as basic programs, applicationprograms, and configuration information for the operation of theterminal. Further, the storage 7 j-30 provides the stored data accordingto the request of the controller 7 j-40.

The controller 7 j-40 includes a multiple connection processor 7 j-42and controls the overall operations of the terminal. For example, thecontroller 7 j-40 transmits and receives a signal through the basebandprocessor 7 j-20 and the RF processor 7 j-10. Further, the controller 7j-40 records and reads data in and from the storage 7 j-30. For thispurpose, the controller 1 j-40 may include at least one processor. Forexample, the controller 7 j-40 may include a communication processor(CP) performing a control for communication and an application processor(AP) controlling a higher layer, such as the application programs.

FIG. 7K is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure.

Referring to FIG. 7K, the base station is configured to include an RFprocessor 7 k-10, a baseband processor 7 k-20, a communication unit 7k-30, a storage 7 k-40, and a controller 7 k-50.

The RF processor 7 k-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 7 k-10 up-converts a baseband signalprovided from the baseband processor 7 k-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 7 k-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC,an ADC, or the like. FIG. 7K illustrates only one antenna but the firstaccess node may include a plurality of antennas. Further, the RFprocessor 7 k-10 may include a plurality of RF chains. Further, the RFprocessor 7 k-10 may perform the beamforming. For the beamforming, theRF processor 1 k-10 may adjust a phase and a size of each of the signalstransmitted/received through a plurality of antennas or antennaelements. The RF processor may perform a downward MIMO operation bytransmitting one or more layers.

The baseband processor 7 k-20 performs a conversion function between thebaseband signal and the bit string according to the physical layerstandard of the first radio access technology. For example, when dataare transmitted, the baseband processor 5 k-20 generates complex symbolsby coding and modulating a transmitted bit string. Further, when dataare received, the baseband processor 7 k-20 recovers the received bitstring by demodulating and decoding the baseband signal provided fromthe RF processor 7 k-10. For example, according to the OFDM scheme, whendata are transmitted, the baseband processor 7 k-20 generates thecomplex symbols by coding and modulating the transmitting bit string,maps the complex symbols to the sub-carriers, and then performs the IFFToperation and the CP insertion to configure the OFDM symbols. Further,when data are received, the baseband processor 7 k-20 divides thebaseband signal provided from the RF processor 7 k-10 in the OFDM symbolunit and recovers the signals mapped to the sub-carriers by the FFToperation and then recovers the receiving bit string by the modulationand decoding. The baseband processor 7 k-20 and the RF processor 7 k-10transmit and receive a signal as described above. Therefore, thebaseband processor 7 k-20 and the RF processor 7 k-10 may be called atransmitter, a receiver, a transceiver, or a communication unit.

The communication unit 7 k-30 provides an interface for performingcommunication with other nodes within the network.

The storage 1 k-40 stores data, such as basic programs, applicationprograms, and configuration information for the operation of the mainbase station. More particularly, the storage 7 k-40 may store theinformation on the bearer allocated to the accessed terminal, themeasured results reported from the accessed terminal, and the like.Further, the storage 7 k-40 may store information that is adetermination criterion on whether to provide a multiple connection tothe terminal or stop the multiple connection to the terminal. Further,the storage 7 k-40 provides the stored data according to the request ofthe controller 7 k-50.

The controller 7 k-50 includes a multiple connection processor 7 k-52and controls the general operations of the main base station. Forexample, the controller 7 k-50 transmits/receives a signal through thebaseband processor 7 k-20 and the RF processor 7 k-10 or thecommunication unit 7 k-30. Further, the controller 7 k-50 records andreads data in and from the storage 7 k-40. For this purpose, thecontroller 1 k-50 may include at least one processor.

The above-mentioned disclosures are summarized as follows. The presentdisclosure relates to a method and apparatus for an operation of an NRPDCP apparatus and an NR RLC apparatus in a next generation mobilecommunication system (hereinafter referred to as NR or 5G), and thepresent disclosure includes the following operations.

Embodiment 7-1 of Terminal NR RLC Operation: Interworking of LTE with NR

The terminal receives the RRC control message for instructing the NR RLCapparatus setup for the predetermined radio bearer from the base station

NR RLC apparatus is generated and is connected to the PDCP apparatus andthe NR MAC apparatus

Data is received through the NR RLC apparatus

The NR RLC processes the data and transfers the processed data to thePDCP apparatus

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the first method is applied toprocess the data

First condition: the NR RLC apparatus is connected to the LTE PDCP andthe NR MAC. Alternatively, the control message for setting up the NR RLCapparatus is received through the LTE.

Second condition: the NR RLC apparatus is connected to the NR PDCP andthe NR MAC. Alternatively, the control message for setting up the NR RLCapparatus is received through the NR.

First method: The received RLC PDU is reassembled into an RLC SDU to betransferred to the PDCP apparatus if the predetermined condition issatisfied. The predetermined condition refers to the case where apredetermined time elapses after there is no non-received RLC PDU or anon-received RLC PDU is generated.

Second method: If the RLC SDU may be reassembled in the received RLCPDU, the RLC SDU is immediately reassembled and is then transferred tothe PDCP apparatus.

Embodiment 7-2 of Terminal NR RLC Operation: NR Standalone

The terminal receives the RRC control message for instructing the NR RLCapparatus setup for the predetermined radio bearer from the base station

NR RLC apparatus is generated and is connected to the NR PDCP apparatusand the NR MAC apparatus

Data is received through the NR RLC apparatus

The NR RLC processes the data and transfers the processed data to the NRPDCP apparatus

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the first method is applied toprocess the data

First condition: The case where the NR RLC apparatus is set in the SRBin the AM mode.

Second condition: The case where the NR RLC apparatus is set in the DRBin the AM mode.

First method: The received RLC PDU is reassembled into an RLC SDU to betransferred to the PDCP device if the predetermined condition issatisfied. The predetermined condition refers to the case where apredetermined time elapses after there is no non-received RLC PDU or anon-received RLC PDU is generated.

Second method: If the RLC SDU may be reassembled in the received RLCPDU, the RLC SDU is immediately reassembled and is then transferred tothe PDCP apparatus.

Embodiment 7-3 of Terminal NR RLC Operation: NR Standalone

The terminal receives the RRC control message for instructing the NR RLCapparatus setup for the predetermined radio bearer from the base station

NR RLC apparatus is generated and is connected to the NR PDCP apparatusand the NR MAC apparatus

Data is received through the NR RLC apparatus

The NR RLC processes the data and transfers the processed data to the NRPDCP apparatus

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the first method is applied toprocess the data

First condition: The case where the NR RLC apparatus is set in the SRBin the AM mode, the case where the NR RLC apparatus is set in the DRB inthe AM mode and receives the information indicating that the firstmethod should be applied from the control message, or the case where theNR RLC apparatus is set in the UM mode.

Second condition: The case where the NR RLC apparatus does not receivefrom the control message the information indicating that the NR RLCapparatus is set in the DRB in the AM mode and applies the first method

First method: The received RLC PDU is reassembled into an RLC SDU to betransferred to the PDCP apparatus if the predetermined condition issatisfied. The predetermined condition refers to the case where apredetermined time elapses after there is no non-received RLC PDU or anon-received RLC PDU is generated.

Second method: If the RLC SDU may be reassembled in the received RLCPDU, the RLC SDU is immediately reassembled and is then transferred tothe PDCP apparatus.

Embodiment 7-4 of Base Station NR RLC Operation: Interworking of LTEwith NR

The NR base station sets the NR RLC apparatus for a predetermined radiobearer.

NR RLC apparatus is generated and is connected to the PDCP device andthe NR MAC device

Data is received through the NR RLC apparatus

The NR RLC processes the data and transfers the processed data to thePDCP apparatus

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the first method is applied toprocess the data

First condition: the NR RLC apparatus is connected to the LTE PDCP andthe NR MAC. Alternatively, the control message for setting up the NR RLCapparatus is received through the LTE.

Second condition: the NR RLC apparatus is connected to the NR PDCP andthe NR MAC. Alternatively, the NR base station itself determines thecontrol message for setting up the NR RLC apparatus is received throughthe NR.

First method: The received RLC PDU is reassembled into an RLC SDU to betransferred to the PDCP apparatus if the predetermined condition issatisfied. The predetermined condition refers to the case where apredetermined time elapses after there is no non-received RLC PDU or anon-received RLC PDU is generated.

Second method: If the RLC SDU may be reassembled in the received RLCPDU, the RLC SDU is immediately reassembled and is then transferred tothe PDCP apparatus.

Embodiment 7-5 of Base Station NR RLC Operation: NR Standalone

The base station sets the NR RLC apparatus for a predetermined radiobearer

NR RLC apparatus is generated and is connected to the NR PDCP apparatusand the NR MAC apparatus

Data is received through the NR RLC apparatus

The NR RLC processes the data and transfers the processed data to the NRPDCP apparatus

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the first method is applied toprocess the data

First condition: The case where the NR RLC apparatus is set in the SRBin the AM mode.

Second condition: The case where the NR RLC apparatus is set in the DRBin the AM mode.

First method: The received RLC PDU is reassembled into an RLC SDU to betransferred to the PDCP apparatus if the predetermined condition issatisfied. The predetermined condition refers to the case where apredetermined time elapses after there is no non-received RLC PDU or anon-received RLC PDU is generated.

Second method: If the RLC SDU may be reassembled in the received RLCPDU, the RLC SDU is immediately reassembled and is then transferred tothe PDCP apparatus.

Embodiment 7-6 of Base Station NR RLC Operation: NR Standalone

The base station sets the NR RLC apparatus for a predetermined radiobearer

NR RLC apparatus is generated and is connected to the NR PDCP apparatusand the NR MAC apparatus

Data is received through the NR RLC apparatus

The NR RLC processes the data and transfers the processed data to the NRPDCP apparatus

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the first method is applied toprocess the data

First condition: The case where the NR RLC apparatus is set in the SRBin the AM mode, the case where the NR RLC apparatus is set in the DRB inthe AM mode, the case where the first method should be applied, or thecase where the NR RLC apparatus is set in the UM mode.

Second condition: The case where the NR RLC apparatus is set in DRB inAM mode and the case where it is determined that the first method is notapplied but the second method is applied

First method: The received RLC PDU is reassembled into an RLC SDU to betransferred to the PDCP apparatus if the predetermined condition issatisfied. The predetermined condition refers to the case where apredetermined time elapses after there is no non-received RLC PDU or anon-received RLC PDU is generated.

Second method: If the RLC SDU may be reassembled in the received RLCPDU, the RLC SDU is immediately reassembled and is then transferred tothe PDCP apparatus.

Embodiment 7-7 of Terminal NR PDCP Operation: Interworking of LTE withNR

The terminal receives the RRC control message for instructing the NRPDCP apparatus setup for the predetermined radio bearer from the basestation

NR PDCP apparatus is generated and is connected to the RLC apparatus

Data is received through the RLC apparatus

The NR PDCP apparatus processes the data and transmits the processeddata to the upper layer or the apparatus

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the first method is applied toprocess the data

The first condition is the case where the NR PDCP apparatus is connectedto the NR RLC apparatus and the LTE RLC apparatus and data is to bereceived through the NR RLC apparatus and the LTE RLC apparatus, thecase where the control message setting the NR PDCP apparatus is receivedthrough the NR and data is set to be received through the NR RLCapparatus and the LTE RLC apparatus, the case where the NR PDCP deviceis connected only to the NR RLC apparatus, or the case where the NR PDCPapparatus is not connected to the LTE base station but is connected toonly the NR base station.

Second condition: The case where the NR PDCP apparatus is connected tothe NR RLC and the LTE RLC and data is set to be received only by theLTE RLC apparatus, or where the control message for setting the NR PDCPapparatus is received through the NR and data is set to be received onlyby the LTE RLC apparatus.

First method: If the predetermined condition is satisfied, the NR PDCPapparatus performs the predetermined processing on the received PDCPPDUs and transfers the processed PDCP PDUs to the upper layer or theapparatus. The predetermined condition is the case where a predeterminedtime has elapsed after a non-received PDCP PDU does not exist or anon-received PDCP PDU is generated. The predetermined processing mayinclude operations of removing the PDCP header from the PDCP PDU,decrypting it, verifying the integrity thereof if necessary, anddecompressing the header of the packet.

Second method: The received PDCP PDUs suffers from the predeterminedprocessing and is transferred to the upper layer or the apparatus. Thepredetermined processing may include operations of removing the PDCPheader from the PDCP PDU, decrypting it, verifying the integrity thereofif necessary, and decompressing the header of the packet.

Embodiment 7-8 of Base Station NR RLC Operation: Interworking of LTEwith NR

The NR base station sets the NR RLC apparatus for a predetermined radiobearer.

NR PDCP apparatus is generated and is connected to the RLC apparatus

Data is received through the RLC apparatus

The NR PDCP apparatus processes the data and transmits the processeddata to the upper layer or the apparatus

If the first condition is satisfied, the first method is applied toprocess the data

If the second condition is satisfied, the first method is applied toprocess the data

First condition: the NR PDCP apparatus is connected to the NR RLCapparatus and the LTE RLC apparatus and is set to receive the datathrough the NR RLC apparatus and the LTE RLC apparatus. Alternatively,the NR base station itself determines the setting of the NR PDCPapparatus and set to receive the data through the NR RLC apparatus andthe LTE RLC apparatus. Alternatively, the case where the NR PDCPapparatus is connected only to the NR RLC apparatus, or the case wherethere is no connection to the LTE base station and the connection toonly the NR base station is set.

Second condition: The NR PDCP apparatus is connected to the NR RLC andthe LTE RLC, and is set to transmit data only to the LTE RLC apparatus.Alternatively, the case where the NR base station itself determines thesetting of the NR PDCP apparatus and data is set to be received only bythe LTE RLC apparatus.

First method: If the predetermined condition is satisfied, the NR PDCPapparatus performs the predetermined processing on the received PDCPPDUs and transfers the processed PDCP PDUs to the upper layer or thedevice. The predetermined condition is the case where a predeterminedtime has elapsed after a non-received PDCP PDU does not exist or anon-received PDCP PDU is generated. The predetermined processing mayinclude operations of removing the PDCP header from the PDCP PDU,decrypting it, verifying the integrity thereof if necessary, anddecompressing the header of the packet.

Second method: The received PDCP PDUs suffers from the predeterminedprocessing and is transferred to the upper layer or the apparatus. Thepredetermined processing may include operations of removing the PDCPheader from the PDCP PDU, decrypting it, verifying the integrity thereofif necessary, and decompressing the header of the packet.

Eighth Embodiment

A term used for identifying a connection node used in the followingdescription, a term referring to network entities, a term referring tomessages, a term referring to an interface between network objects, aterm referring to various identification information, or the like areillustrated for convenience of explanation. Accordingly, the presentdisclosure is not limited to terms to be described below and other termsindicating objects having the equivalent technical meaning may be used.

Hereafter, for convenience of explanation, the present disclosure usesterms and names defined in the 3GPP LTE. However, the present disclosureis not limited to the terms and names but may also be identicallyapplied to the system according to other standards.

FIG. 8A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure.

Referring to FIG. 8A, a radio access network of an LTE system isconfigured to include next generation base stations (evolved node B,hereinafter, eNB, Node B, or base station) 8 a-05, 8 a-10, 8 a-15, and 8a-20, a mobility management entity (MME) 8 a-25, and a serving-gateway(S-GW) 8 a-30. User equipment (hereinafter, UE or terminal) 8 a-35accesses an external network through the eNBs 8 a-05 to 8 a-20 and theS-GW 8 a-30.

Referring to FIG. 8A, the eNB 8 a-05 to 8 a-20 correspond to theexisting node B of the UMTS system. The eNB is connected to the UE 8a-35 through a radio channel and performs more complicated role than theexisting node B. In the LTE system, in addition to a real-time servicelike a voice over Internet protocol (VoIP) through the Internetprotocol, all the user traffics are served through a shared channel andtherefore an apparatus for collecting and scheduling status information,such as a buffer status, an available transmission power status, and achannel state of the UEs is required. Here, the eNBs 8 a-05 to 8 a-20take charge of the collecting and scheduling. One eNB generally controlsa plurality of cells. For example, to implement a transmission rate of100 Mbps, the LTE system uses, as a radio access technology, OFDM in,for example, a bandwidth of 20 MHz. Further, an adaptive modulation &coding (hereinafter, called AMC) determining a modulation scheme and achannel coding rate depending on a channel status of the terminal isapplied. The S-GW-30 is an apparatus for providing a data bearer andgenerates or removes the data bearer according to the control of the MME8 a-25. The MME is an apparatus for performing a mobility managementfunction for the terminal and various control functions and is connectedto a plurality of base stations.

FIG. 8B is a diagram illustrating a radio protocol structure in an LTEsystem according to an embodiment of the present disclosure.

Referring to FIG. 8B, the radio protocol of the LTE system is configuredto include PDCPs 8 b-05 and 8 b-40, RLCs 8 b-10 and 8 b-35, and mediumaccess controls (MMCs) 8 b-15 and 8 b-30 in the terminal and the eNB,respectively. The PDCPs 8 b-05 and 8 b-40 are in charge of operations,such as IP header compression/decompression. The main functions of thePDCP are summarized as follows.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

Un-sequence delivery function (In-sequence delivery of upper layer PDUsat PDCP re-establishment procedure for RLC AM)

Reordering function (For split bearers in DC (only support for RLC AM):PDCP PDU routing for transmission and PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs atPDCP re-establishment procedure for RLC AM)

Retransmission function (Retransmission of PDCP SDUs at handover and,for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure,for RLC AM)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink)

The RLCs 8 b-10 and 8 b-35 reconfigures the PDCP PDU to an appropriatesize to perform the ARQ operation or the like. The main functions of theRLC are summarized as follows.

Data transfer function (Transfer of upper layer PDUs)

ARQ function (Error Correction through ARQ (only for AM data transfer))

Concatenation, segmentation, reassembly functions (Concatenation,segmentation and reassembly of RLC SDUs (only for UM and AM datatransfer))

Re-segmentation function (Re-segmentation of RLC data PDUs (only for AMdata transfer))

Reordering function (Reordering of RLC data PDUs (only for UM and AMdata transfer))

Duplicate detection function (Duplicate detection (only for UM and AMdata transfer))

Error detection function (Protocol error detection (only for AM datatransfer))

RLC SDU discard function (RLC SDU discard (only for UM and AM datatransfer))

RLC re-establishment function (RLC re-establishment)

The MACs 8 b-15 and 8 b-30 are connected to several RLC layer devicesconfigured in one terminal and perform an operation of multiplexing RLCPDUs into an MAC PDU and demultiplexing the RLC PDUs from the MAC PDU.The main functions of the MAC are summarized as follows.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing/demultiplexing function (Multiplexing/demultiplexing of MACSDUs belonging to one or different logical channels into/from transportblocks (TB) delivered to/from the physical layer on transport channels)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

Physical layers 8 b-20 and 8 b-25 perform an operation of channel-codingand modulating higher layer data, making the higher layer data as anOFDM symbol and transmitting them to a radio channel, or demodulatingand channel-decoding the OFDM symbol received through the radio channeland transmitting the demodulated and channel-decoded OFDM symbol to thehigher layer.

FIG. 8C is a diagram illustrating a structure of a next generationmobile communication system according to an embodiment of the presentdisclosure.

Referring to FIG. 8C, a radio access network of a next generation mobilecommunication system (hereinafter referred to as NR or 5G) is configuredto include a next generation base station (New radio node B, hereinafterNR gNB or NR base station) 8 c-10 and a new radio core network (NR CN) 8c-05. The user terminal (new radio user equipment, hereinafter, NR UE orUE) 8 c-15 accesses the external network through the NR gNB 8 c-10 andthe NR CN 8 c-05.

Referring to FIG. 8C, the NR gNB 8 c-10 corresponds to an evolved node B(eNB) of the existing LTE system. The NR gNB is connected to the NR UE 8c-15 via a radio channel and may provide a service superior to theexisting node B. In the next generation mobile communication system,since all user traffics are served through a shared channel, anapparatus for collecting state information, such as a buffer state, anavailable transmission power state, and a channel state of the UEs toperform scheduling is required. The NR NB 8 c-10 may serve as thedevice. One NR gNB generally controls a plurality of cells. In order torealize high-speed data transmission compared with the current LTE, theNR gNB may have an existing maximum bandwidth or more, and may beadditionally incorporated into a beam-forming technology may be appliedby using OFDM as a radio access technology 8 c-20. Further, an adaptivemodulation & coding (hereinafter, called AMC) determining a modulationscheme and a channel coding rate depending on a channel status of theterminal is applied. The NR CN 8 c-05 may perform functions, such asmobility support, bearer setup, QoS setup, and the like. The NR CN is adevice for performing a mobility management function for the terminaland various control functions and is connected to a plurality of basestations. In addition, the next generation mobile communication systemcan interwork with the existing LTE system, and the NR CN is connectedto the MME 8 c-25 through the network interface. The MME is connected tothe eNB 8 c-30 which is the existing base station.

FIG. 8D is a diagram illustrating a radio protocol structure of a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 8D, the radio protocol of the next generation mobilecommunication system is configured to include NR PDCPs 8 d-05 and 8d-40, NR RLCs 8 d-10 and 8 d-35, and NR MACs 8 d-15 and 8 d-30 in theterminal and the NR base station. The main functions of the NR PDCPs 8d-05 and 8 d-40 may include some of the following functions.

Header compression and decompression function (Header compression anddecompression: ROHC only)

Transfer function of user data (Transfer of user data)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Reordering function (PDCP PDU reordering for reception)

Duplicate detection function (Duplicate detection of lower layer SDUs)

Retransmission function (Retransmission of PDCP SDUs)

Ciphering and deciphering function (Ciphering and deciphering)

Timer-based SDU discard function (Timer-based SDU discard in uplink))

In this case, the reordering function of the NR PDCP apparatus refers toa function of rearranging PDCP PDUs received in a lower layer in orderbased on a PDCP sequence number (SN) and may include a function oftransferring data to a higher layer in the rearranged order, a functionof recording PDCP PDUs lost by the reordering, a function of reporting astate of the lost PDCP PDUs to a transmitting side, and a function ofrequesting a retransmission of the lost PDCP PDUs.

The main functions of the NR RLCs 8 d-10 and 8 d-35 may include some ofthe following functions.

Data transfer function (Transfer of upper layer PDUs)

In-sequence delivery function (In-sequence delivery of upper layer PDUs)

Out-of-sequence delivery function (Out-of-sequence delivery of upperlayer PDUs)

ARQ function (Error correction through HARQ)

Concatenation, segmentation, reassembly function (Concatenation,segmentation and reassembly of RLC SDUs)

Re-segmentation function (Re-segmentation of RLC data PDUs)

Reordering function (Reordering of RLC data PDUs)

Duplicate detection function (Duplicate detection)

Error detection function (Protocol error detection)

RLC SDU discard function (RLC SDU discard)

RLC re-establishment function (RLC re-establishment)

In the above description, the in-sequence delivery function of the NRRLC apparatus refers to a function of delivering RLC SDUs received froma lower layer to a higher layer in order, and may include a function ofreassembling and transferring an original one RLC SDU which is dividedinto a plurality of RLC SDUs and received, a function of rearranging thereceived RLC PDUs based on the RLC sequence number (SN) or the PDCPsequence number (SN), a function of recording the RLC PDUs lost by thereordering, a function of reporting a state of the lost RLC PDUs to thetransmitting side, a function of requesting a retransmission of the lostRLC PDUs, a function of transferring only the SLC SDUs before the lostRLC SDU to the higher layer in order when there is the lost RLC SDU, afunction of transferring all the received RLC SDUs to the higher layerbefore a predetermined timer starts if the timer expires even if thereis the lost RLC SDU, or a function of transferring all the RLC SDUsreceived until now to the higher layer in order if the predeterminedtimer expires even if there is the lost RLC SDU. In this case, theout-of-sequence delivery function of the NR RLC apparatus refers to afunction of directly delivering the RLC SDUs received from the lowerlayer to the higher layer regardless of order, and may include afunction of reassembling and transferring an original one RLC SDU whichis divided into several RLC SDUs and received, and a function of storingthe RLC SN or the PDCP SP of the received RLC PDUs and arranging it inorder to record the lost RLC PDUs.

The NR MACs 8 d-15 and 8 d-30 may be connected to several NR RLC layerapparatus configured in one terminal, and the main functions of the NRMAC may include some of the following functions.

Mapping function (Mapping between logical channels and transportchannels)

Multiplexing and demultiplexing function (Multiplexing/demultiplexing ofMAC SDUs)

Scheduling information reporting function (Scheduling informationreporting)

HARQ function (Error correction through HARQ)

Priority handling function between logical channels (Priority handlingbetween logical channels of one UE)

Priority handling function between terminals (Priority handling betweenUEs by means of dynamic scheduling)

MBMS service identification function (MBMS service identification)

Transport format selection function (Transport format selection)

Padding function (Padding)

The NR PHY layers 8 d-20 and 8 d-25 may perform an operation ofchannel-coding and modulating higher layer data, making the higher layerdata as an OFDM symbol and transmitting them to a radio channel, ordemodulating and channel-decoding the OFDM symbol received through theradio channel and transmitting the demodulated and channel-decoded OFDMsymbol to the higher layer.

FIG. 8E is a diagram illustrating a first MAC PDU structure for a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 8E, if the MAC transmitting side receives the RLC PDU(or MAC SDU) from the RLC layer, the MAC transmitting side inserts anidentifier (local channel identity, hereinafter, referred to as LCID) ofRLC entity generated by the RLC PDU (or MAC SDU) and a size (length,hereinafter, referred to as an L-field) of the RLC PDU into the MACheader. The LCID and the L-field are inserted one by one per RLC PDU,and therefore if the plurality of RLC PDUs are multiplexed into the MACPDU, the LCID and the L-field may also be inserted by the number of RLCPDUs.

Since the information of the MAC header is usually located at the frontpart of the MAC PDU, the LCID and the L-fields are matched with the RLCPDU (or MAC SDU) within the header in order. In other words, MACsub-header 1 indicates information on MAC SDU 1, and MAC sub-header 2indicates information on MAC SDU 2.

For the operation of the physical layer, a total size of the MAC PDU isgiven to the receiving side as separate control information. Since thetotal size of the MAC PDU is a quantized value according to apredetermined criterion, padding may be used in some cases. The paddingmeans certain bits (usually ‘0’) that are filled in the remaining partof the packet so that when the packet is generated with data, the sizeof the packet is byte-aligned.

Since the total size of the MAC PDU is given, an L-field valueindicating the size of the RLC PDU (or MAC SDU) may be unnecessaryinformation in some cases. For example, if only one RLC PDU is stored inthe MAC PDU, the size of the RLC PDU has the possibility that the sizeof the MAC header is equal to a limited value in the size of the MACPDU.

Meanwhile, the VoIP packet consists of an IP/UDP/RTP header and a VoIPframe, and the IP/UDP/RTP header is compressed to about 1 to 15 bytesthrough a header compression protocol called a robust header compression(ROHC) and the size of the VoIP frame always has a constant value withina given code rate. Therefore, the size of the VoIP packet does notdeviate from a certain range, and it is effective to use a predeterminedvalue rather than informing a value each time like the L-field.

The following Table 8 describes the information that may be included inthe MAC header.

TABLE 8 Variables in MAC Header Variable Usage LCID The LCID mayindicate the identifier of the RLC entity that generates the RLC PDU (orMAC SDU) received from the upper layer. Alternatively, the LCID mayindicate the MAC control element (CE) or the padding. Further, the LCIDmay be defined differently depending on the channel to be transmitted.For example, the LCID may be defined differently according to DL-SCH,UL-SCH, and MCH. L The L may indicate a length of the MAC SDU, and mayindicate a length of the MAC CE having a variable length. In the case ofthe MAC CE having a fixed length, the L-field may be omitted. TheL-field may be omitted for predetermined reasons. The predeterminedreasons are the case where the size of the MAC SDU is fixed, the size ofthe MAC PDU is informed from the transmitting side to the receivingside, or the length may be calculated by calculation at the receivingside. F The F indicates the size of the L-field. If there is no L-field,the F may be omitted, and if there is the F-field, the size of theL-field can be limited to a predetermined size. F2 The F2 indicates thesize of the L-field. If there is no L-field, the F2 may be omitted, andif there is the F2-field, the size of the L-field may be limited to apredetermined size and the L-field may be limited to a size differentfrom the F-field. For example, the F2-field may indicate a larger sizethan the F- field. E E indicates other headers in the MAC heater. Forexample, if the E has a value of 1, variables of another MAC header maybe come. However, if the E has a value of 0, the MAC SDU, the MAC CE, orthe Padding may be come. R Reserved bit.

Meanwhile, the embodiment of the configuration and transmission of theMAC PDU of the terminal or the base station described below may beinterpreted as an operation between the transmitting end and thereceiving end. In other words, the process of transmitting the uplinkMAC PDU configured by the terminal which is the transmitting end to thebase station which is the receiving end may be applied to the process oftransmitting the downlink MAC PDU configured by the base station whichis the transmitting end to the terminal which is the receiving end.

Referring to FIG. 8E, 8e-(Format 1-1) may store one MAC SDU or MAC CE.In the above structure, the MAC header is located at a front part andthe payload is located at a rear part. The header may include thevariables described in Table 8 except for the L-field, and informationother than the variables described in Table 8.

8e-(Format 1-2a) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC CE, the MAC SDU, andthe padding. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 8e-(Format1-2a). The 8e-(Format 1-2a) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

8e-(Format 1-2b) has a structure in which the MAC header is located atthe front part of the MAC PDU, followed by the MAC CE, the MAC SDU, andthe padding. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 8e-(Format1-2a). In the 8e-(Format 1-2a) structure, the L-field may be included inall the sub-headers.

FIGS. 8FA to 8FI are diagrams illustrating a second MAC PDU structurefor a next generation mobile communication system according to anembodiment of the present disclosure.

Referring to FIGS. 8FA to 8FF-(Format 2-1) may store one MAC SDU or MACCE. In the above structure, the payload is located at a front part andthe MAC header is located at a rear part. The header may include thevariables described in Table 8 except for the L-field, and informationother than the variables described in Table 8.

8f-(Format 2-2a) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format8-2a). The 8f-(Format 2-2a) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

8f-(Format 2-2b) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 8f-(Format2-2b). The 8f-(Format 2-2b) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

8f-(Format 2-2c) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 8f-(Format2-2b). In the 8f-(Format 2-2c) structure, the L-field may be included inall the sub-headers.

8f-(Format 2-2d) has a structure in which the MAC SDU, the MAC CE, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC SDU, MAC CE, and padding, in theorder numbered on the sub-headers and the payloads of the 8f-(Format2-2d). In the 8f-(Format 2-2d) structure, the L-field may be included inall the sub-headers.

8f-(Format 2-2e) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 8f-(Format2-2e). The 8f-(Format 2-2e) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

8f-(Format 2-2f) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 2f-(Format8-2f). The 8f-(Format 2-2f) structure is characterized in that anL-field is not included in the last sub-header. The receiving side mayconfirm the L-field value of the remaining sub-headers and subtract theL-field value from the entire length of the MAC PDU to estimate thelength of the MAC SDU.

8f-(Format 2-2g) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 8f-(Format2-2g). In the 3f-(Format 2-2g) structure, the L-field may be included inall the sub-headers.

8f-(Format 2-2h) has a structure in which the MAC CE, the MAC SDU, andthe padding are located at the front part of the MAC PDU, followed bythe MAC header. The MAC header consists of several sub-heads. Thesub-header may include some of the variables described in Table 8, andinformation other than the variables described in Table 8. The paddingis stored only when necessary for predetermined reasons. Thepredetermined reasons refer to a case where it is necessary to set thebyte MAC PDU in byte units. In this case, each MAC sub-head indicatesinformation corresponding to each MAC CE, MAC SDU, and padding, in theorder numbered on the sub-headers and the payloads of the 8f-(Format2-2h). In the 8f-(Format 2-2h) structure, the L-field may be included inall the sub-headers.

8f-(Format 2-2i) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 8, and informationother than the variables described in Table 8. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 8f-(Format 2-2i).The 8f-(Format 2-2i) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

8f-(Format 2-2j) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 8, and informationother than the variables described in Table 8. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 8-2i).The 8f-(Format 2-2j) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

8f-(Format 2-2k) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 8, and informationother than the variables described in Table 8. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 2f-(Format 8-2k). Inthe 8f-(Format 2-2k) structure, the L-field may be included in all thesub-headers.

8f-(Format 2-2l) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 8, and informationother than the variables described in Table 8. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 8f-(Format 2-2l). Inthe 8f-(Format 2-2l) structure, the L-field may be included in all thesub-headers.

8f-(Format 2-2m) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 8, and informationother than the variables described in Table 8. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 8f-(Format 2-2m).The 8f-(Format 2-2m) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

8f-(Format 2-2n) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 8, and informationother than the variables described in Table 8. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 8f-(Format 2-2n).The 8f-(Format 2-2n) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

8f-(Format 2-2o) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 8, and informationother than the variables described in Table 8. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 8f-(Format 2-2o). Inthe 8f-(Format 2-2o) structure, the L-field may be included in all thesub-headers.

8f-(Format 2-2p) has a structure in which the MAC SDU, the padding, andthe MAC CE are located at the front part of the MAC PDU, followed by theMAC header. The MAC header consists of several sub-heads. The sub-headermay include some of the variables described in Table 8, and informationother than the variables described in Table 8. The padding is storedonly when necessary for predetermined reasons. The predetermined reasonsrefer to a case where it is necessary to set the byte MAC PDU in byteunits. In this case, each MAC sub-head indicates informationcorresponding to each MAC SDU, padding, and MAC CE, in the ordernumbered on the sub-headers and the payloads of the 8f-(Format 2-2p). Inthe 8f-(Format 2-2p) structure, the L-field may be included in all thesub-headers.

FIG. 8G is a diagram illustrating a third MAC PDU structure for a nextgeneration mobile communication system according to an embodiment of thepresent disclosure.

Referring to FIG. 8G, 8g-(Format 3-1) may store one MAC SDU or MAC CE.In the above structure, the MAC header is located at a front part andthe payload is located at a rear part. The header may include thevariables described in Table 8 except for the L-field, and informationother than the variables described in Table 8.

8g-(Format 3-2a) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 8FA to 2FI, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the second MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The sub-header may include some of thevariables described in Table 8, and information other than the variablesdescribed in Table 8. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,MAC CE, and padding, in the order numbered on the sub-headers and thepayloads of the 8g-(Format 3-2a). For example, the header of the frontpart becomes the information indicating the payload of the rear part.The 8g-(Format 3-2a) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

8g-(Format 3-2b) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 8FA to 8FI, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the second MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The sub-header may include some of thevariables described in Table 8, and information other than the variablesdescribed in Table 8. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,MAC CE, and padding, in the order numbered on the sub-headers and thepayloads of the 8g-(Format 3-2b). For example, the header of the frontpart becomes the information indicating the payload of the rear part. Inthe 8g-(Format 3-2b) structure, the L-field may be included in all thesub-headers.

8g-(Format 3-2c) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 8FA to 8FI, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the second MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The sub-header may include some of thevariables described in Table 8, and information other than the variablesdescribed in Table 8. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,MAC CE, and padding, in the order numbered on the sub-headers and thepayloads of the 8g-(Format 3-2c). For example, the header of the frontpart becomes the information indicating the payload of the rear part.The 8g-(Format 3-2c) structure is characterized in that an L-field isnot included in the last sub-header. The receiving side may confirm theL-field value of the remaining sub-headers and subtract the L-fieldvalue from the entire length of the MAC PDU to estimate the length ofthe MAC SDU.

8g-(Format 3-2c) has a structure, such as the sub-header, the MAC CE,the sub-header, the MAC SDU, the sub-header, and the padding, and inFIGS. 8FA to 8FI, the second MAC PDU structure has the structure inwhich the sub-headers are collected at one part and the payload part islocated separately, whereas the second MAC PDU structure has therepeating structure, such as the sub-header, the payload, thesub-header, and the payload. The sub-header may include some of thevariables described in Table 8, and information other than the variablesdescribed in Table 8. The padding is stored only when necessary forpredetermined reasons. The predetermined reasons refer to a case whereit is necessary to set the byte MAC PDU in byte units. In this case,each MAC sub-head indicates information corresponding to each MAC SDU,MAC CE, and padding, in the order numbered on the sub-headers and thepayloads of the 8g-(Format 3-2d). For example, the header of the frontpart becomes the information indicating the payload of the rear part. Inthe 8g-(Format 3-2d) structure, the L-field may be included in all thesub-headers.

A preferred 8-1-th embodiment of the present disclosure for selecting aMAC PDU structure in the next generation mobile communication system isas follows.

The 8-1-th embodiment is a method for determining a MAC PDU format to beapplied to an arbitrary MAC PDU by a terminal among a plurality ofpredefined MAC PDU formats.

If the MAC PDU is received from the base station and a 1-1-th conditionis satisfied, a 1-1-th format is applied.

If the MAC PDU is received from the base station and a 1-2-th conditionis satisfied, a 1-2-th format is applied.

If a 2-1-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-1-th format is applied.

If a 2-2-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-2-th format is applied.

The 1-1-th condition is the case where only one MAC SDU is stored in theMAC PDU and no padding or MAC CE is stored,

The 1-2-th condition refers to the case where one or more MAC SDU isstored in the MAC PDU or the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together.

The 1-1-th format refers to the 8e-(Format 1-1) of FIG. 8E as a formatin which the MAC sub-header is located before the associated MAC SDU andthe information indicating the size of the MAC SDU is not included inthe MAC sub-header.

The 1-2-th format refers to the 8e-(Format 1-2a) or the 8e-(Format 1-2b)of FIG. 8E as a format in which the MAC sub-header is located before theassociated MAC SDU and the information indicating the size of the MACSDU is not included in the MAC sub-header.

In the 2-1-th condition is the case where only one MAC SDU is stored inthe MAC PDU and the padding or the MAC CE is not received or the casewhere the MAC PDU is transmitted during the random access process or theCCCH control message is stored in the MAC PDU.

The 2-2-th condition refers to the case where one or more MAC SDU isstored in the MAC PDU or the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together.

The 2-1-th format refers to the 8e-(Format 2-1) of FIG. 8E as a formatin which the MAC sub-header is located before the associated MAC SDU andthe information indicating the size of the MAC SDU is not included inthe MAC sub-header.

The 2-2-th format refers to 8f-(Format 2-2a) or 8f-(Format 2-2b) or8f-(Format 2-2c) or 8f-(Format 2-2d) or 8f (Format 2-2d), 8f-(Format2-2e) or 8f-(Format 2-2f) or 8f-(Format 2-2g) or 8f-(Format 2-2h) or8f-(Format 2-2i) or 8f-(Format 2-2j) or 8f-(Format 2-2k) or 8f-(Format2-2) or 8f-(Format 2-2m) or 8f-(Format 2-2n) or 8f-(Format 2-2o) or 8f(Format 2-2p) of FIGS. 8FA to 8FI.

FIG. 8H is a diagram illustrating an operation of a terminal in a nextgeneration mobile communication system according to 8-1-th and 8-2-thembodiments of the present disclosure.

Referring to FIG. 8H, the terminal 8 h-01 confirms whether the MAC PDUis received or not or the generation of the MAC PDU is instructed inoperation 8 h-05). If the MAC PDU is received, the 1-1-th and 1-2-thconditions are confirmed in operation 8 h-10. If the 1-1-th condition issatisfied, the 1-1-th format is applied in operation 8 h-20, and if the1-2-th condition is satisfied, the 1-2-th format is applied in operation8 h-15. If the MAC PDU should be generated, the 2-1-th and 2-2-thconditions are confirmed in operation 8 h-25. If the 2-1-th condition issatisfied, the 2-1-th format is applied in operation 8 h-30, and if the2-2-th condition is satisfied, the 2-2-th format is applied in operation8 h-35.

A preferred 8-2-th embodiment of the present disclosure for selecting aMAC PDU structure in the next generation mobile communication system isas follows.

The 8-2-th embodiment is a method for determining a MAC PDU format to beapplied to an arbitrary MAC PDU by a terminal among a plurality ofpredefined MAC PDU formats.

If the MAC PDU is received from the base station and a 1-1-th conditionis satisfied, a 1-1-th format is applied.

If the MAC PDU is received from the base station and a 1-2-th conditionis satisfied, a 1-2-th format is applied.

If a 2-1-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-1-th format is applied.

If a 2-2-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-2-th format is applied.

The 1-1-th condition is the case where only one MAC SDU is stored in theMAC PDU and no padding or MAC CE is stored,

The 1-2-th condition refers to the case where one or more MAC SDU isstored in the MAC PDU or the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together.

The 1-1-th format refers to the 8e-(Format 1-1) of FIG. 8E as a formatin which the MAC sub-header is located before the associated MAC SDU andthe information indicating the size of the MAC SDU is not included inthe MAC sub-header.

The 1-2-th format refers to the 8e-(Format 1-2a) or the 8e-(Format 1-2b)of FIG. 8E as a format in which the MAC sub-header is located before theassociated MAC SDU and the information indicating the size of the MACSDU is not included in the MAC sub-header.

In the 2-1-th condition is the case where only one MAC SDU is stored inthe MAC PDU and the padding or the MAC CE is not received or the casewhere the MAC PDU is transmitted during the random access process or theCCCH control message is stored in the MAC PDU.

The 2-2-th condition refers to the case where one or more MAC SDU isstored in the MAC PDU or the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together.

The 2-1-th format refers to the 8g-(Format 3-1) of FIG. 8G as a formatin which the MAC SDU associated with the MAC sub-header is repeatedlylocated and the information indicating the size of the MAC SDU is notincluded in the MAC sub-header.

The 2-2-th format refers to 8G-(Format 3-2a) or 8g-(Format 3-2b) or8g-Format 3-2c) of FIG. 8G as a format in which MAC SDU associated withthe MAC sub-header are repeatedly located and the information indicatingthe size of the MAC SDU is included in the MAC sub-header.

The operation of the terminal of the 8-2-th embodiment is the same asFIG. 8H. The terminal 8 h-01 confirms whether the MAC PDU is received ornot or the generation of the MAC PDU is instructed (8 h-05). If the MACPDU is received, the 1-1-th and 1-2-th conditions are confirmed (8h-10). If the 1-1-th condition is satisfied, the 1-1-th format isapplied (8 h-20), and if the 1-2-th condition is satisfied, the 1-2-thformat is applied (8 h-15). If the MAC PDU should be generated, the2-1-th and 2-2-th conditions are confirmed (8 h-25). If the 2-1-thcondition is satisfied, the 2-1-th format is applied (8 h-30), and ifthe 2-2-th condition is satisfied, the 2-2-th format is applied (8h-35).

FIG. 8I is a diagram illustrating an operation of a terminal in a nextgeneration mobile communication system according to 8-3-th and 8-4-thembodiments of the present disclosure.

Referring to FIG. 8I, in an embodiment of the present disclosure, anessential parameter set (the set is referred to as numerology) isdefined, and it is assumed that the essential parameter set is anefficient system that maintains compatibility between the transmittingend and the receiving end. The essential parameter set may include asubcarrier interval, a CP length, and the like. In the next generationmobile system, a plurality of numerologies may exist and may coexist inone cell. One cell may support at least one numerology, and the cellwill need to efficiently notify terminals within a service area of thecell of the supportable numerology. One set of numerologies may beconfigured of several elements, that is, a combination of a frequencybandwidth, sub-carrier spacing, a cyclic prefix (CP) length, a subframelength, and the like. Accordingly, there will be many kinds of possiblenumerologies. In the 8-3-th embodiment, the numerology is defined toinclude subcarrier spacing among the above elements, and the subcarrierspacing may be 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, and960 kHz. Some of the assumed carrier spacings may be limited as having asmall numerology, and the other may be limited having a largenumerology.

The 8-3-th embodiment is a method for determining a MAC PDU format to beapplied to an arbitrary MAC PDU by a terminal among a plurality ofpredefined MAC PDU formats.

If the MAC PDU is received from the base station and a 1-1-th conditionis satisfied, a 1-1-th format is applied.

If the MAC PDU is received from the base station and a 1-2-th conditionis satisfied, a 1-2-th format is applied.

If a 2-1-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-1-th format is applied.

If a 2-2-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-2-th format is applied.

If a 2-3-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-3-th format is applied.

The 1-1-th condition is the case where only one MAC SDU is stored in theMAC PDU and no padding or MAC CE is stored,

The 1-2-th condition refers to the case where one or more MAC SDU isstored in the MAC PDU or the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together.

The 1-1-th format refers to the 8e-(Format 1-1) of FIG. 8E as a formatin which the MAC sub-header is located before the associated MAC SDU andthe information indicating the size of the MAC SDU is not included inthe MAC sub-header.

The 1-2-th format refers to the 8e-(Format 1-2a) or the 8e-(Format 1-2b)of FIG. 8E as a format in which the MAC sub-header is located before theassociated MAC SDU and the information indicating the size of the MACSDU is not included in the MAC sub-header.

In the 2-1-th condition is the case where only one MAC SDU is stored inthe MAC PDU and the padding or the MAC CE is not received or the casewhere the MAC PDU is transmitted during the random access process or theCCCH control message is stored in the MAC PDU.

The 2-2 condition refers to the case where one or more MAC SDU isincluded in the MAC PDU, the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together, and the numerologyreceived on the PDCCH is small or the numerology of a resource allocatedto an uplink grant is small.

The 2-3 condition refers to the case where one or more MAC SDU isincluded in the MAC PDU, the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together, and the numerologyreceived on the PDCCH is large or the numerology of a resource allocatedto an uplink grant is large.

The 2-1-th format refers to the 8e-(Format 2-1) of FIG. 8E as a formatin which the MAC sub-header is located before the associated MAC SDU andthe information indicating the size of the MAC SDU is not included inthe MAC sub-header.

The 2-2-th format refers to the 8e-(Format 1-2a) or the 8e-(Format 1-2b)of FIG. 8E as a format in which the MAC sub-header is located before theassociated MAC SDU and the information indicating the size of the MACSDU is not included in the MAC sub-header.

The 2-3-th format refers to 8f-(Format 2-2a) or 8f-(Format 2-2b) or8f-(Format 2-2c) or 8f-(Format 2-2d) or 8f (Format 2-2d), 8f-(Format2-2e) or 8f-(Format 2-2f) or 8f-(Format 2-2g) or 8f-(Format 2-2h) or8f-(Format 2-2i) or 8f-(Format 2-2j) or 8f-(Format 2-2k) or 8f-(Format2-2l) or 8f-(Format 2-2m) or 8f-(Format 2-2n) or 8f-(Format 2-2o) or8f-(Format 2-2p) of FIGS. 8FA to 8FI as a formation in which the MACsub-header is located after the associated MAC SDU and the informationindicating the size of the MAC SDU is included in the MAC sub-header.

The operation of the terminal of the 8-3-th embodiment is the same asFIG. 8H. The terminal 8 h-01 confirms whether the MAC PDU is received ornot or the generation of the MAC PDU is instructed in operation 8 h-05.If the MAC PDU is received, the 1-1-th and 1-2-th conditions areconfirmed in operation 8 i-10. If the 1-1-th condition is satisfied, the1-1-th format is applied in operation 8 h-20, and if the 1-2-thcondition is satisfied, the 1-2-th format is applied in operation 8i-15. If the MAC PDU should be generated, the 2-1-th condition, the2-2-th condition, and the 2-3 condition are confirmed in operation 8i-25. If the 2-1-th condition is satisfied, the 2-1-th format is appliedin operation 8 i-30, and if the 2-2-th condition is satisfied, the2-2-th format is applied in operation 8 i-35. If the 2-3-th condition issatisfied, the 2-3-th formation is applied in operation 8 i-40.

A preferred 8-4-th embodiment of the present disclosure for selecting aMAC PDU structure in the next generation mobile communication system isas follows.

In an embodiment of the present disclosure, an essential parameter set(the set is referred to as numerology) is defined, and it is assumedthat the essential parameter set is an efficient system that maintainscompatibility between the transmitting end and the receiving end. Theessential parameter set may include a subcarrier interval, a CP length,and the like. In the next generation mobile system, a plurality ofnumerologies may exist and may coexist in one cell. One cell may supportat least one numerology, and the cell will need to efficiently notifyterminals within a service area of the cell of the supportablenumerology. One set of numerologies may be configured of severalelements, that is, a combination of a frequency bandwidth, sub-carrierspacing, a cyclic prefix (CP) length, a subframe length, and the like.Accordingly, there will be many kinds of possible numerologies. In the8-3-th embodiment, the numerology is defined to include subcarrierspacing among the above elements, and the subcarrier spacing may be 15kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, and 960 kHz. Some of theassumed carrier spacings may be limited as having a small numerology,and the other may be limited having a large numerology.

The 8-4-th embodiment is a method for determining a MAC PDU format to beapplied to an arbitrary MAC PDU by a terminal among a plurality ofpredefined MAC PDU formats.

If the MAC PDU is received from the base station and a 1-1-th conditionis satisfied, a 1-1-th format is applied.

If the MAC PDU is received from the base station and a 1-2-th conditionis satisfied, a 1-2-th format is applied.

If a 2-1-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-1-th format is applied.

If a 2-2-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-2-th format is applied.

If a 2-3-th condition is satisfied when the MAC PDU to be transmitted tothe base station is generated, a 2-3-th format is applied.

The 1-1-th condition is the case where only one MAC SDU is stored in theMAC PDU and no padding or MAC CE is stored,

The 1-2-th condition refers to the case where one or more MAC SDU isstored in the MAC PDU or the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together.

The 1-1-th format refers to the 8e-(Format 1-1) of FIG. 8E as a formatin which the MAC sub-header is located before the associated MAC SDU andthe information indicating the size of the MAC SDU is not included inthe MAC sub-header.

The 1-2-th format refers to the 8e-(Format 1-2a) or the 8e-(Format 1-2b)of FIG. 8E as a format in which the MAC sub-header is located before theassociated MAC SDU and the information indicating the size of the MACSDU is not included in the MAC sub-header.

In the 2-1-th condition is the case where only one MAC SDU is stored inthe MAC PDU and the padding or the MAC CE is not received or the casewhere the MAC PDU is transmitted during the random access process or theCCCH control message is stored in the MAC PDU.

The 2-2 condition refers to the case where one or more MAC SDU isincluded in the MAC PDU, the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together, and the numerologyreceived on the PDCCH is small or the numerology of a resource allocatedto an uplink grant is small.

The 2-3 condition refers to the case where one or more MAC SDU isincluded in the MAC PDU, the MAC SDU and the MAC CE are stored together,or the MAC SDU and the padding are stored together, and the numerologyreceived on the PDCCH is large or the numerology of a resource allocatedto an uplink grant is large.

The 2-1-th format refers to the 8e-(Format 2-1) of FIG. 8E as a formatin which the MAC sub-header is located before the associated MAC SDU andthe information indicating the size of the MAC SDU is not included inthe MAC sub-header.

The 2-2-th format refers to the 8e-(Format 1-2a) or the 8e-(Format 1-2b)of FIG. 8E as a format in which the MAC sub-header is located before theassociated MAC SDU and the information indicating the size of the MACSDU is not included in the MAC sub-header.

The 2-3-th format refers to 8G-(Format 3-2a) or 8g-(Format 3-2b) or8g-Format 3-2c) of FIG. 8G as a format in which MAC SDU associated withthe MAC sub-header are repeatedly located and the information indicatingthe size of the MAC SDU is included in the MAC sub-header.

The operation of the terminal of the 8-4-th embodiment is the same asFIG. 8H. The terminal 8 h-01 confirms whether the MAC PDU is received ornot or the generation of the MAC PDU is instructed in operation 8 h-05.If the MAC PDU is received, the 1-1-th and 1-2-th conditions areconfirmed in operation 8 i-10. If the 1-1-th condition is satisfied, the1-1-th format is applied in operation 8 h-20, and if the 1-2-thcondition is satisfied, the 1-2-th format is applied in operation 8i-15. If the MAC PDU should be generated, the 2-1-th condition, the2-2-th condition, and the 2-3 condition are confirmed in operation 8i-25. If the 2-1-th condition is satisfied, the 2-1-th format is appliedin operation 8 i-30, and if the 2-2-th condition is satisfied, the2-2-th format is applied in operation 8 i-35. If the 2-3-th condition issatisfied, the 2-3-th formation is applied in operation 8 i-40.

A preferred 8-5-th embodiment of the present disclosure for selecting aMAC PDU structure in the next generation mobile communication system isas follows.

The operation when the terminal receives the RRC control message(RRCConnectionSetup message or RRCConnectionReconfiguration message)indicating the predetermined MAC entity setting from the base stationwill be described.

The terminal applies the first format if the predetermined firstcondition is satisfied.

The terminal applies the first format if the predetermined firstcondition is satisfied.

The first condition refers to the case where the terminal is instructedthe LTE MAC entity in the control message for setting the MAC entity.

The second condition refers to the case where the terminal is instructedthe LTE MAC entity from the control message for setting the MAC entity.

The first format refers to 8e-(Format 1-1) of FIG. 8E as the format inwhich the MAC sub-header is located before the associated MAC SDU andthe information indicating the size of the MAC SDU is not included inthe MAC sub-header or 8e-(Format 1-2a) or 8e-(Format 1-2b) of FIG. 8E asa format in which the information indicating the size of the MAC SDU isincluded in the MAC sub-header.

The second format refers to 8f-(Format 2-2a) or 8f-(Format 2-2b) or8f-(Format 2-2c) or 8f-(Format 2-2d) or 8f (Format 2-2d), 8f-(Format2-2e) or 8f-(Format 2-2f) or 8f-(Format 2-2g) or 8f-(Format 2-2h) or8f-(Format 2-2i) or 8f-(Format 2-2j) or 8f-(Format 2-2k) or 8f-(Format2-2l) or 8f-(Format 2-2m) or 8f-(Format 2-2n) or 8f-(Format 2-2o) or 8f(Format 2-2p) of FIGS. 8FA to 8FI as a format in which the MACsub-header is located after the associated MAC SDU and the informationindicating the size of the MAC SDU is included in the MAC sub-header orrefers to 8g-(Format 3-2a) or 8g-(Format 3-2b) or 8g-(Format 3-2c) or8g-(Format 3-2d) of FIG. 8G as a format in which the informationindicating the size of the MAC SDU is included in the MAC sub-header.

FIG. 8J is a diagram illustrating an operation of a terminal in a nextgeneration mobile communication system according to an 8-5-th embodimentof the present disclosure.

Referring to FIG. 8J, the terminal confirms the first condition or thesecond condition in operation 8 j-05, and if the first condition issatisfied, proceeds to operation 8 j-10 to apply the first format and ifthe second condition is satisfied, proceeds to operation 8 j-15 to applythe second format.

Hereinafter, the present disclosure proposes an efficient RLC layerheader structure and a segmentation operation.

In a 8-6-th embodiment of the present disclosure, a procedure forsegmenting or concatenating packets received from the upper layer in theRLC layer is proposed.

FIG. 8K is a diagram illustrating a process of performing, by an RLClayer, segmentation or concatenation in a 8-6-th according to anembodiment of the present disclosure.

Referring to FIG. 8K, a process of performing segmentation orconcatenation by the RLC layer in the 8th to 6th embodiments of thepresent disclosure is illustrated. The RLC SDU is processed to be a sizeindicated by the MAC layer. For this purpose, the RLC SDU is segmentedor concatenated with segments of other RLC SDUs or other RLC SDUs. Inthis example, an AMD PDU to which ARQ is applied is considered. In theinitial transmission, the segments of two RLC SDU # 1 and RLC SDU # 2configure one RLC PDU. The RLC PDU includes an RLC header 8 k-15 and anRLC payload 8 k-20. The RLC header includes the character of the RLC PDUand segmentation or concatenation information. For example, an examplethereof may include a D/C field, an RF field, the FI field, an SN field,an LI field, and the like.

The D/C (Data/Control) field is 1 bit and is used to indicate whetherthe configured RLC PDU is a control PDU or a data PDU.

Value Description 0 Control PDU 1 Data PDU

The re-segmentation flag (RF) field is 1 bit and is used to indicatewhether the configured RLC PDU is an AMD PDU or an AMD PDU segment.

Value Description 0 AMD PDU 1 AMD PDU segment

The framing info (FI) field is 2 bits and is used to indicate whetherthe start and end parts of the RLC PDU data field are the start and endpart of the original RLC SDU, to indicate whether the RLC SDU is notsegmented or the RLC SDU segment is the start or end or middle part ofthe original RLC SDU.

Value Description 00 First byte of the Data field corresponds to thefirst byte of a RLC SDU. Last byte of the Data field corresponds to thelast byte of a RLC SDU. 01 First byte of the Data field corresponds tothe first byte of a RLC SDU. Last byte of the Data field does notcorrespond to the last byte of a RLC SDU. 10 First byte of the Datafield does not correspond to the first byte of a RLC SDU. Last byte ofthe Data field corresponds to the last byte of a RLC SDU. 11 First byteof the Data field does not correspond to the first byte of a RLC SDU.Last byte of the Data field does not correspond to the last byte of aRLC SDU.

A sequence number (SN) field is a sequence number of the RLC PDU.

A length indicator (LI) field is 11 bits in the case of RLC UM and 15bits in the case of RLC AM and is used to indicate the size of theconfigured RLC SDU or RLC SDU segment. Therefore, the LI field should beincluded in proportion to the number of RLC SDU or RLC SDU segmentsincluded in one RLC PDU.

In FIG. 8K, the RLC payload consists of segments of RLC SDU # 1 and RLCSDU # 2, and a boundary of the two parts is indicated by X1 (8 k-25).The RLC PDU thus configured is transferred to the MAC layer. However,the RLC PDU may not be successfully retransmitted and may beretransmitted according to the ARQ operation of the RLC layer. For theARQ retransmission, the RLC PDU may be re-segmented again. In order todistinguish it from the existing AMD PDU, it is referred to as the AMDPDU segment. For example, the AMD PDU that is retransmitted after thetransmission but failed can be retransmitted to two AMD PDU segments maybe retransmitted into two AMD PDU segments while being segmented becausethe transmission resources that can be transmitted at the retransmissiontime are smaller than the transmission resources at the time of thefirst transmission. The first AMD PDU segment transmits a Y1-sized RLCpayload part 8 k-35 of a basic AMD PDU, and the second AMD PDU segmenttransmits the remaining RLC payload part excluding the Y1 size. Thesecond AMD PDU segment includes a part (X1-Y1) 8 k-25 and 8 k-35 of theoriginal RLC SDU # 1 8 k-05 and a part of the RLC SDU # 2 8 k-10. TheADM PDU segment includes RLC headers 8 k-30 and 8 k-40, and includes theD/C field, the RF field, the FI field, the SN field, the LSF field, theSO field, the LI field, and the like, and Z1 8 k-45. As compared withthe AMD PDU, an LSF field, and an SO field may be further included.

A last segment flag (LSF) field is 1 bit and is used to indicate whetherthe last byte of the AMD PDU segment matches the last byte of the AMDPDU.

Value Description 0 Last byte of the AMD PDU segment does not correspondto the last byte of an AMD PDU. 1 Last byte of the AMD PDU segmentcorresponds to the last byte of an AMD PDU.

A segment offset (SO) field is 15 or 16 fields and is used to indicateat which of the AMD PDU the AMD PDU segment is located. For example, theSO value in the first AMD PDU segment header of the example is 0 bytes,and the SO value in the second AMD PDU segment header is Y1. The valuesof the fields included in the headers of the AMD PDU, the first ADM PDUsegment, and the second ADM PDU segment may refer to 8 k-50, 8 k-55, and8 k-60.

FIG. 8L illustrates an RLC header structure according to an 8-6-thembodiment of the present disclosure.

Referring to FIG. 8L, an RLC header structure is illustrated assumingthat the RLC SN is 16 bits and the LI field is 15 bits in the 8-6-thembodiments of the present disclosure, and 8I-01 represents one exampleof the RLC header structure for the AMD PDU described in FIG. 8K and8I-02 may be an example of the RLC header structure for the AMD PDUsegment described above. The RLC header structure may include some ofthe fields described above with reference to FIG. 8K or other newfields, and may have a different structure depending on the lengths ofthe respective fields, such as other RLC SN lengths and other LI fieldlengths. R may be a reserved bit, and a P field may be a field forrequesting a status report to a corresponding RLC entity of thereceiving end. For example, if 0, the status report is not requested,and if 1, the status report may be requested. The status report mayinclude information on data received so far. The E field may indicatewhether the data field is located immediately after the fixed RLC headerpart of the header or the E field, or whether the E field or the L fieldis located. For example, if the E field is 0, it indicates whether adata field is located immediately after the fixed RLC header part or theE field, and if the E field is 1, it indicates whether another E fieldor L field is located immediately after the fixed RLC header part or theE field.

In an 8-7-th embodiment of the present disclosure, a procedure forsegmenting packets received from the upper layer in the RLC layerwithout concatenation is proposed.

FIG. 8M is a diagram illustrating an SO-based segmentation procedureaccording to an 8-7-th embodiment of the present disclosure.

Referring to FIG. 8M, the SO-based segmentation procedure may becharacterized in that there is no RF field and FI field unlike theprocedure of FIG. 8K according to the 8-6-th embodiment of the presentdisclosure. In addition, the RLC header used for the first transmissionand the RLC header used for the retransmission are not distinguishedfrom each other and a combined header is used. In addition, theconcatenation is not performed in the RLC layer. If the RLC layerreceives the RLC SDU of 8 m-05, the RLC layer directly inserts the RLCSN into the RLC SDU, generates the fixed RLC header, and forms the RLCPDU. If the segmentation is required for a predetermined reason, the RLCPDU may be generated by updating the SO field and the LSF field, such as8 m-10 or 8 m-15. The fixed RLC header may include an SN field, an SOfield, an LSF field, or another field. The predetermined reason may beby way of example the case where the size of the RLC PDU or the size ofthe RLC PDU currently generated is larger than the size of thetransmission resource allocated in the MAC layer. The sequence number(SN) field is a sequence number of the RLC PDU, or may reuse the PDCP SNif necessary or set. The SO field is a field having a predeterminedlength, and in the first transmission, the SO field may indicate howmany bytes of the original RLC PDU data field (RLC SDU) the first byteof the RLC PDU data field (RLC SDU) is, and even in the retransmission,the SO field may indicate how many bytes of the original RLC PDU datafield the first byte of the re-segmented RLC PDU data field is. The lastsegment flag (LSF) field is 1 bit and is used to indicate whether thelast byte of the segmented or re-segmented RLC PDU data field matchesthe last byte of the original RLC PDU data field.

Value Description 0 Last byte of the AMD PDU segment does not correspondto the last byte of an AMD PDU. 1 Last byte of the AMD PDU segmentcorresponds to the last byte of an AMD PDU.

If the RLC PDUs of 8 m-10 and 8 m-15 fail to be transmitted, theretransmission may be performed. At this time, if the transmissionresource is insufficient, the re-segmentation may be performed like as 8m-20, 8 m-25 and 8 m-30. The SO field and the LSF field of the RLC PDUs8 m-20, 8 m-25 and 8 m-30 newly generated when the re-segmentation isperformed.

FIG. 8N illustrates an RLC header structure according to an 8-7-thembodiment of the present disclosure.

Referring to FIG. 8N illustrates an RLC header structure assuming thecase where the RLC SN is 16 bits and the LI field is 15 bits in the 8-7embodiment of the present disclosure, in which 8 n-01 may be an exampleof the RLC header structure for the SO-based segmentation described withreference to FIG. 8m . The RLC header structure may include some of thefields described above with reference to FIG. 8m or other new fields,and may have a different structure depending on the lengths of therespective fields, such as other RLC SN lengths and an SO field lengthand the locations of the respective fields. R may be a reserved bit, anda P field may be a field for requesting a status report to acorresponding RLC entity of the receiving end. For example, if 0, thestatus report is not requested, and if 1, the status report may berequested. The status report may include information on data received sofar. The RLC header structure may have no RF field, FI field, or Efield. In addition, the RLC header used for the first transmission andthe RLC header used for the retransmission are not distinguished fromeach other and a combined header is used.

In a 8-8-th embodiment of the present disclosure, another procedure forsegmenting packets received from the upper layer in the RLC layerwithout concatenation is proposed.

FIG. 8O is a diagram illustrating a segmentation control information(SCI)-based segmentation procedure according to an 8-8-th embodiment ofthe present disclosure.

Referring to FIG. 8O, the SCI-based segmentation procedure may becharacterized in that there is no RF field and FI field unlike theprocedure of FIG. 8K according to the 8-6-th embodiment of the presentdisclosure and a new field called SCI is included. It has an advantageof being able to reduce the overhead of the RLC header with slightlymore complexity compared to the procedure of the 8-7-th embodiment ofthe present disclosure. In addition, the RLC header used for the firsttransmission and the RLC header used for the retransmission are notdistinguished from each other. In addition, the RLC header structure forthe complete RLC SDU without segmentation and the segmented first RLCSDU segment and the RLC header structure for the segmented middle orlast RLC SDU segment are differentiated from each other. In addition,the concatenation is not performed in the RLC layer. If the RLC layerreceives the RLC SDU of 8 o-05, the RLC layer directly inserts the RLCSN into the RLC SDU, generates the fixed RLC header, and forms the RLCPDU. If the segmentation is required for a predetermined reason, the RLCPDU may be generated by updating the SCI field and the SO field, such as8 o-10 or 8 o-15. The fixed RLC header may include an SN field, an SCIfield, an SO field, or another field. The predetermined reason may be byway of example the case where the size of the RLC PDU or the size of theRLC PDU currently generated is larger than the size of the transmissionresource allocated in the MAC layer. The sequence number (SN) field is asequence number of the RLC PDU, or may reuse the PDCP SN if necessary orset. The SO field is a field having a predetermined length, and in thefirst transmission, the SO field may indicate how many bytes of theoriginal RLC PDU data field (RLC SDU) the first byte of the RLC PDU datafield (RLC SDU) is, and even in the retransmission, the SO field mayindicate how many bytes of the original RLC PDU data field the firstbyte of the re-segmented RLC PDU data field is. The length of the SOfield may be set by an RRC message (e.g., RRCConnectionSetup orRRCConnectionReconfiguration message). For example, the length of the SOfield may be set differently for each bearer. For example, in a service,such as VoLTE and VoIP, it is possible to set the SO field to 1 byte andset the SO field to 2 bytes in case of the eMBB service. In addition, apredetermined bit before the SO field is defined, and the predeterminedbit may indicate the length of the SO field. For example, if it isassumed that a predetermined bit is 1 bit, 0 may indicate an SO fieldhaving a length of 1 byte, and 1 may indicate an SO field having 2bytes. In the above description, the SCI field may be defined asfollows, and the field name SCI may be named by another name, such assegmentation information (SI), framing Information (FI), or segmentationcontrol (SC)

Value Description 00 A complete RLC PDU 01 First segment of a RLC PDU 10Last segment of a RLC PDU 11 Middle segment of a RLC PDU

If the SCI field is 00, it represents the complete RLC PDU withoutsegmentation. In this case, the SO field is not required for the RLCheader. If the SCI field is 01, it represents the segmented first RLCPDU segment. In this case, the SO field is not required for the RLCheader. If the SCI field is 10, it represents the segmented last RLC PDUsegment. In this case, the SO field is required for the RLC header. Ifthe SCI field is 11, it represents the segmented middle RLC PDU segment.In this case, the SO field is required for the RLC header. The mappingrelationship between the 2 bits and the 4 information (complete RLC PDU,first segment, last segment, middle segment) may be 4×3×2×1=24 in total,and one example of the total of mapping relationships is shown. Thepresent disclosure includes all of 24 mapping relationships. If the RLCPDUs of 8 o-10 and 8 o-15 fail to be transmitted, the retransmission maybe performed. At this time, if the transmission resource isinsufficient, the re-segmentation may be performed like as 8 o-20, 8o-25, and 8 o-30. The SO field and the LSF field of the RLC PDUs 8 o-20,8 o-25 and 8 o-30 newly generated when the re-segmentation may beupdated. 8 o-20 is the first segment, and therefore the SCI is updatedto 01 and no SO field is required.

Meanwhile, the above-mentioned SCI field (or, SI field, FI field, or SCfield) may also be based on the RLC SDU. In other words, if the SCIfield is 00, it represents the complete RLC SDU that is not segmented.In this case, the SO field is not required for the RLC header. If theSCI field is 01, it represents the segmented first RLC PDU segment. Inthis case, the SO field is not required for the RLC header. If the SCIfield is 10, it represents the segmented last RLC PDU segment. In thiscase, the SO field is required for the RLC header. If the SCI field is11, it represents the segmented middle RLC PDU segment. In this case,the SO field is required for the RLC header. 8 o-25 is the middlesegment, and therefore, the SCI is updated to 11, and the SO field isupdated to 300 to indicate how many bytes of the original RLC PDU datafield (RLC SDU) the first byte of the RLC PDU data field (RLC SDU). 8o-30 is the last segment, and therefore, the SCI is updated to 10, andthe SO field is updated to 600 to indicate how many bytes of theoriginal RLC PDU data field (RLC SDU) the first byte of the RLC PDU datafield (RLC SDU).

FIG. 8P illustrates an RLC header structure according to an 8-8-thembodiment of the present disclosure.

Referring to FIG. 8P, an RLC header structure is illustrated assumingthe case where the RLC SN is 16 bits and the LI field is 15 bits in the8-8-th embodiment of the present disclosure, in which 8 p-01 may be anexample of the RLC header structure for the SCI-based segmentationdescribed with reference to FIG. 8P. The RLC header structure mayinclude some of the fields described above with reference to FIG. 8O orother new fields, and may have a different structure depending on thelengths of the respective fields, such as other RLC SN lengths and an SOfield length and the locations of the respective fields. R may be areserved bit, and a P field may be a field for requesting a statusreport to a corresponding RLC entity of the receiving end. For example,if 0, the status report is not requested, and if 1, the status reportmay be requested. The status report may include information on datareceived so far. The RLC header structure may have no RF field, FIfield, or E field. In addition, the RLC header used for the firsttransmission and the RLC header used for the retransmission are notdistinguished from each other and a combined header is used.

If the information indicated by the SCI field indicates a complete RLCPDU (e.g., SCI=00) or the information indicated by the SCI fieldindicates the segmented first RLC PDU segment (e.g., SCI=01), like 8p-01, the RLC header structure without an SO field may be used. As oneexample, the RLC header structure of the 8 p-01 may include some of thefields described with reference to FIG. 8O or other new fields, and mayhave a different structure depending on the lengths of the respectivefields, such as other RLC SN lengths and the locations of the respectivefields.

Under the assumption that the terminal and the network have promised touse a predetermined SO field length in the procedure of 8 o or theterminal is instructed the length information on the SO field for eachbearer as the RRC message, if the information indicated by the SCI fieldindicates the segmented middle or last RLC PDU segment (for example,SCI=10 or 11), like 8 p-02, the RLC header structure with the SO fieldmay be used. As one example, the RLC header structure of the 8 p-02 mayinclude some of the fields or other new fields, and may have a differentstructure depending on the lengths of the respective fields, such asother RLC SN lengths and the SO field length and the locations of therespective fields.

Under the assumption that the terminal and the network do not promise touse a predetermined SO field length in the procedure of 8 o or theterminal does not instruct the length information on the SO field foreach bearer as the RRC message, if the information indicated by the SCIfield is newly defined and promised to be used, the informationindicated by the SCI field indicates the segmented middle or last RLCPDU segment (for example, SCI=10 or 11), like 8 p-03, the RLC headerstructure with the LI field and the SO field may be used. As oneexample, the RLC header structure of the 8 p-03 may include some of thefields or other new fields, and may have a different structure dependingon the lengths of the respective fields, such as other RLC SN lengthsand the LI field length and the locations of the respective fields. TheLI field may indicate the length of the SO field. For example, if it isassumed that the LI field is 1 bit, 0 may indicate an SO field having alength of 1 byte, and 1 may indicate an SO field having 2 bytes. The LIfield may be preset as a predetermined length

In a 8-9-th embodiment of the present disclosure, another procedure forsegmenting packets received from the upper layer in the RLC layerwithout concatenation is proposed.

FIG. 8Q illustrates an SI, FI, LSF-based segmentation procedureaccording to an 8-9-th embodiment of the present disclosure.

Referring to FIG. 8Q, the SI, FI, and LSF-based segmentation proceduremay be characterized in that there is no RF field and FI field unlikethe procedure of FIG. 8K according to the 8-6-th embodiment of thepresent disclosure, and a new SI field and an FI field are defined andthe fields are used. In addition, the RLC header used for the firsttransmission and the RLC header used for the retransmission are notdistinguished from each other. In addition, the RLC header structure forthe complete RLC SDU without segmentation and the segmented first RLCSDU segment and the RLC header structure for the segmented middle orlast RLC SDU segment are differentiated from each other. In addition,the concatenation is not performed in the RLC layer. If the RLC layerreceives the RLC SDU of 8 q-05, the RLC layer directly inserts the RLCSN into the RLC SDU, generates the fixed RLC header, and forms the RLCPDU. If the segmentation is required for a predetermined reason, the RLCPDU may be generated by updating the SCI field and the FI field, such as8 q-10 or 8 q-15. The middle or last segment of the RLC PDU may have theSO field and the LSF field. The fixed RLC header may include an SNfield, an SI field, an FI field, an SO field, an LSF field, or anotherfield. The predetermined reason may be by way of example the case wherethe size of the RLC PDU or the size of the RLC PDU currently generatedis larger than the size of the transmission resource allocated in theMAC layer. The sequence number (SN) field is a sequence number of theRLC PDU, or may reuse the PDCP SN if necessary or set. The SO field is afield having a predetermined length, and in the first transmission, theSO field may indicate how many bytes of the original RLC PDU data field(RLC SDU) the first byte of the RLC PDU data field (RLC SDU) is, andeven in the retransmission, the SO field may indicate how many bytes ofthe original RLC PDU data field the first byte of the re-segmented RLCPDU data field is. The length of the SO field may be set by an RRCmessage (e.g., RRCConnectionSetup or RRCConnectionReconfigurationmessage). For example, the length of the SO field may be set differentlyfor each bearer. For example, in a service, such as VoLTE and VoIP, itis possible to set the SO field to 1 byte and set the SO field to 2bytes in case of the eMBB service. In addition, a predetermined bitbefore the SO field is defined, and the predetermined bit may indicatethe length of the SO field. For example, if it is assumed that apredetermined bit is 1 bit, 0 may indicate an SO field having a lengthof 1 byte, and 1 may indicate an SO field having 2 bytes. In the abovedescription, the SI field may be defined as follows, and the field nameSI may be named by any other name.

Value Description 0 No segmentation 1 Segmentation

If the SI field is 0, it indicates that segmentation is not performedand indicates a complete RLC PDU. In this case, the SO field and the LSFfield are not required for the RLC header. If the SI field is 1, itindicates that segmentation is performed, and may indicate the segmentedfirst RLC PDU segment, middle RLC PDU segment, or last RLC PDU segment.The mapping relationship of 1 bit and 2 information (No Segmentation orSegmentation) may be 2×1=2 in total, and one example of the total ofmapping relationships is shown. The present disclosure includes all of 2mapping relationships.

In the above description, the FI field may be defined as follows, andthe field name FI may be named by any other name.

Value Description 0 First segment of a RLC PDU 1 Middle segment of a RLCPDU or Last segment of a RLC PDU

If the FI field is 0, it represents the segmented first RLC PDU segment.In this case, the SO field and the LSF field are not required for theRLC header. If the FI field is 1, it represents the segmented middle orlast RLC PDU segment. In this case, the LSF field and the SO field isrequired for the RLC header. If the FI field is 1 and the LSF field is0, it indicates the segmented middle RLC PDU segment, if the FI field is1 and the LSF field is 1, it indicates the segmented last RLC PDUsegment, and the mapping relationship of 1 bit and two information(first segment or middle/last segment) may be 2×1=2 in total, and oneexample of the total of mapping relationships is shown. The presentdisclosure includes all of 2 mapping relationships. The mappingrelationship of 1 bit and 2 information (middle segment or last segment)may be 2×1=2 in total, and one example of the total of mappingrelationships is shown. The present disclosure includes all of 2 mappingrelationships.

If the RLC PDUs of 8 q-10 and 8 q-15 fail to be transmitted, theretransmission may be performed. At this time, if the transmissionresource is insufficient, the re-segmentation may be performed like as 8q-20, 8 q-25, and 8 q-30. The SI field, the FI field, the LSF field, andthe SO field of the RLC PDUs 8 q-20, 8 q-25 and 8 q-30 newly generatedwhen the re-segmentation may be updated. 8 q-20 is the segmented firstsegment, and therefore SI is updated to 1 and FI is updated to 0 and theSO field and the LSF field are not required. 8 o-25 is the segmentedmiddle segment, and therefore the SI is updated to 1, FI is updated to1, and the LSF is updated to 0, and the SO field is updated to 300 toindicate how many bytes of the original RLC PDU data field (RLC SDU) thefirst byte of the RLC PDU data field (RLC SDU) is. 8 q-30 is thesegmented last segment, and therefore the SI is updated to 1, FI isupdated to 1, and the LSF is updated to 1, and the SO field is updatedto 600 to indicate how many bytes of the original RLC PDU data field(RLC SDU) the first byte of the RLC PDU data field (RLC SDU) is.

FIG. 8R illustrates an RLC header structure according to an 8-9-thembodiment of the present disclosure.

Referring to FIG. 8R, an RLC header structure is illustrated assumingthe case where the RLC SN is 16 bits and the LI field is 15 bits in the8-9-th embodiment of the present disclosure, in which 8 r-01 may be anexample of the RLC header structure for the SI, FI, and LSF-basedsegmentation described with reference to FIG. 8Q. The RLC headerstructure may include some of the fields described above with referenceto FIG. 8Q or other new fields, and may have a different structuredepending on the lengths of the respective fields, such as other RLC SNlengths and an SO field length and the locations of the respectivefields. R may be a reserved bit, and a P field may be a field forrequesting a status report to a corresponding RLC entity of thereceiving end. For example, if 0, the status report is not requested,and if 1, the status report may be requested. The status report mayinclude information on data received so far. The RLC header structuremay have no RF field and FI field (meaning of 2-bit FI of FIG. 8L), or Efield. In addition, the RLC header used for the first transmission andthe RLC header used for the retransmission are not distinguished fromeach other and a combined header is used.

If the information indicated by the SCI field indicates a complete RLCPDU (e.g., SI=00) without being segmented or the information indicatedby the FI field indicates the segmented last RLC PDU segment (e.g.,FI=0), like 8 r-01, the RLC header structure without the LSF field andthe SO field may be used. As one example, the RLC header structure ofthe 8 r-01 may include some of the fields described with reference toFIG. 8Q or other new fields, and may have a different structuredepending on the lengths of the respective fields, such as other RLC SNlengths and the locations of the respective fields.

Under the assumption that the terminal and the network are promised touse a predetermined SO field length in the procedure of 8 q or theterminal is instructed the length information on the SO field for eachbearer as the RRC message, if the information indicated by the SCI fieldis segmented (for example, SI=1) and the information indicated by the FIfield indicates the segmented middle or last RLC PDU segment (forexample, FI=1), like 8 r-02, the RLC header structure with the LSF fieldand the SO field may be used. As one example, the RLC header structureof the 8 r-02 may include some of the fields described with reference toFIG. 8Q or other new fields, and may have a different structuredepending on the lengths of the respective fields, such as other RLC SNlengths and the SO field length and the locations of the respectivefields.

Under the assumption that the terminal and the network have promised touse a predetermined SO field length in the procedure of 8 q or theterminal does not instruct the length information on the SO field foreach bearer as the RRC message, if the LI field indicating the length ofthe SO field is newly defined and promised to be used, it indicates thatthe information indicated by the SI field is segmented (e.g., SI=1), andif the information indicated by the FI field indicates the segmentedmiddle or last RLC PDU segment (e.g., FI=1), like 8 p-03, the RLC headerstructure with the LSF field and the SO field may be used. As oneexample, the RLC header structure of the 8 r-03 may include some of thefields described with reference to FIG. 8Q or other new fields, and mayhave a different structure depending on the lengths of the respectivefields, such as other RLC SN lengths and the LI field length and thelocations of the respective fields. The LI field may indicate the lengthof the SO field. For example, if it is assumed that the LI field is 1bit, 0 may indicate an SO field having a length of 1 byte, and 1 mayindicate an SO field having 2 bytes. The LI field may be preset as apredetermined length.

As can be appreciated from the above embodiments, the apparatus forperforming transmission (terminal in the uplink and base station in thedownlink) determines whether or not the RLC SDU received in the RLC PDUis segmented according to the characteristics of the RLC PDU, and ifsegmented, determines whether the SO field is stored or not depending onthe first segment. In other words, if the apparatus performing thetransmission is not segmented, even though segmented, the SO field isnot stored in the case of a first segment and an SO field is stored inthe case of the middle segment or the last segment. The apparatus (basestation in the uplink and terminal in the downlink) performing thereception checks the header field of the received packet, and if the RLCSDU stored in the received RLC PDU is an the RLC SDU which is notsegmented or the first segment, it is determined that the RLC SDU or thesegment is stored immediately after the RLC header without the SO field,so that the RLC SDU is reassembled or the received RLC SDU istransferred to the upper layer. It is determined that there is an SOfield stored in the received RLC PDU, and the RLC SDU is reassembledaccording to the value of the stored SO field and transferred to theupper layer.

FIG. 8S is a block diagram illustrating an internal structure of aterminal according to an embodiment of the present disclosure.

Referring to FIG. 8S, the terminal includes a radio frequency (RF)processor 8 s-10, a baseband processor 8 s-20, a storage 8 s-30, and acontroller 8 s-40.

The RF processor 8 s-10 serves to transmit and receive a signal througha radio channel, such as band conversion and amplification of a signal.For example, the RF processor 8 s-10 up-converts a baseband signalprovided from the baseband processor 8 s-20 into an RF band signal andthen transmits the RF band signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 8 s-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, adigital to analog converter (DAC), an analog to digital converter (ADC),or the like. FIG. 8S illustrates only one antenna but the terminal mayinclude a plurality of antennas. Further, the RF processor 8 s-10 mayinclude a plurality of RF chains. Further, the RF processor 8 s-10 mayperform beamforming. For the beamforming, the RF processor 8 s-10 mayadjust a phase and a size of each of the signals transmitted andreceived through a plurality of antennas or antenna elements. Inaddition, the RF processor may perform MIMO and may receive a pluralityof layers when performing a MIMO operation. The RF processor 8 sj-10 mayperform reception beam sweeping by appropriately configuring a pluralityof antennas or antenna elements under the control of the controller oradjust a direction and a beam width of the reception beam so that thereception beam is resonated with the transmission beam.

The baseband processor 8 s-20 performs a conversion function between abaseband signal and a bit string according to a physical layer standardof a system. For example, when data are transmitted, the basebandprocessor 8 s-20 generates complex symbols by coding and modulating atransmitted bit string. Further, when data are received, the basebandprocessor 8 s-20 recovers the received bit string by demodulating anddecoding the baseband signal provided from the RF processor 8 s-10. Forexample, according to the OFDM scheme, when data are transmitted, thebaseband processor 2 i-20 generates the complex symbols by coding andmodulating the transmitting bit string, maps the complex symbols tosub-carriers, and then performs an inverse fast Fourier transform (IFFT)operation and a cyclic prefix (CP) insertion to construct the OFDMsymbols. Further, when data are received, the baseband processor 8 s-20divides the baseband signal provided from the RF processor 8 s-10 in anOFDM symbol unit and recovers the signals mapped to the sub-carriers bya fast Fourier transform (FFT) operation and then recovers the receivedbit string by the modulation and decoding.

The baseband processor 8 s-20 and the RF processor 8 s-10 transmit andreceive a signal as described above. Therefore, the baseband processor 4h-20 and the RF processor 4 h-10 may be called a transmitter, areceiver, a transceiver, or a communication unit. Further, at least oneof the baseband processor 8 s-20 and the RF processor 8 s-10 may includea plurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 8 s-20 and the RF processor 8 s-10 may include differentcommunication modules to process signals in different frequency bands.For example, the different wireless access technologies may include anLTE network, an NR network, and the like. Further, different frequencybands may include a super high frequency (SHF) (for example: 2.5 GHz, 5GHz) band, a millimeter wave (for example: 60 GHz) band.

The storage 8 s-30 stores data, such as basic programs, applicationprograms, and configuration information for the operation of theterminal. The storage 8 s-30 provides the stored data according to therequest of the controller 8 s-40.

The controller 8 s-40 includes a multiple connection processor 8 s-42and controls the overall operations of the terminal. For example, thecontroller 8 s-40 transmits and receives a signal through the basebandprocessor 8 s-20 and the RF processor 8 s-10. Further, the controller 8s-40 records and reads data in and from the storage 8 s-30. For thispurpose, the controller 8 s-40 may include at least one processor. Forexample, the controller 8 s-40 may include a communication processor(CP) performing a control for communication and an application processor(AP) controlling an upper layer, such as the application programs.

FIG. 8T is a block diagram illustrating a configuration of a basestation transceiver according to an embodiment of the presentdisclosure.

Referring to FIG. 8T, the base station is configured to include an RFprocessor 8 t-10, a baseband processor 8 t-20, a communication unit 8t-30, a storage 8 t-40, and a controller 8 t-50.

The RF processor 8 t-10 serves to transmit/receive a signal through aradio channel, such as band conversion and amplification of a signal.For example, the RF processor 8 t-10 up-converts a baseband signalprovided from the baseband processor 8 t-20 into an RF band signal andthen transmits the baseband signal through an antenna and down-convertsthe RF band signal received through the antenna into the basebandsignal. For example, the RF processor 8 t-10 may include a transmittingfilter, a receiving filter, an amplifier, a mixer, an oscillator, a DAC,an ADC, and the like. FIG. 8T illustrates only one antenna but the firstaccess node may include a plurality of antennas. Further, the RFprocessor 5I-10 may include the plurality of RF chains. Further, the RFprocessor 8 t-10 may perform the beamforming. For the beamforming, theRF processor 5I-10 may adjust a phase and a size of each of the signalstransmitted and received through a plurality of antennas or antennaelements. The RF processor may perform a downward MIMO operation bytransmitting one or more layers.

The baseband processor 8 t-20 performs a conversion function between thebaseband signal and the bit string according to the physical layerstandard of the first radio access technology. For example, when dataare transmitted, the baseband processor 8 t-20 generates complex symbolsby coding and modulating a transmitting bit string. Further, when dataare received, the baseband processor 8 t-20 recovers the receiving bitstring by demodulating and decoding the baseband signal provided fromthe RF processor 8 t-10. For example, according to the OFDM scheme, whendata are transmitted, the baseband processor 8 t-20 generates thecomplex symbols by coding and modulating the transmitting bit string,maps the complex symbols to the sub-carriers, and then performs the IFFToperation and the CP insertion to configure the OFDM symbols. Further,when data are received, the baseband processor 8 t-20 divides thebaseband signal provided from the RF processor 8 t-10 in an OFDM symbolunit and recovers the signals mapped to the sub-carriers by an FFToperation and then recovers the receiving bit string by the modulationand decoding. The baseband processor 8 t-20 and the RF processor 8 t-10transmit and receive a signal as described above. Therefore, thebaseband processor 8 t-20 and the RF processor 8 t-10 may be called atransmitter, a receiver, a transceiver, a communication unit, or awireless communication unit.

The communicator 8 t-30 provides an interface for performingcommunication with other nodes within the network.

The storage 8 t-40 stores data, such as basic programs, applicationprograms, and configuration information for the operation of the mainbase station. More particularly, the storage 8 t-40 may store theinformation on the bearer allocated to the accessed terminal, themeasured results reported from the accessed terminal, and the like.Further, the storage 8 t-40 may store information that is adetermination criterion on whether to provide a multiple connection tothe terminal or stop the multiple connection to the terminal. Further,the storage 8 t-40 provides the stored data according to the request ofthe controller 8 t-50.

The controller 8 t-50 includes a multiple connection processor 8 t-52and controls the general operations of the main base station. Forexample, the controller 8 t-50 transmits/receives a signal through thebaseband processor 8 t-20 and the RF processor 85-10 or the communicator8 t-30. Further, the controller 8 t-50 records and reads data in andfrom the storage 8 t-40. For this purpose, the controller 8 t-50 mayinclude at least one processor.

Ninth Embodiment

Hereinafter, an operation principle of the present disclosure will bedescribed in detail with reference to the accompanying drawings.Hereinafter, when it is determined that the detailed description of theknown art related to the present disclosure may obscure the gist of thepresent disclosure, the detailed description thereof will be omitted.Further, the following terminologies are defined based on the functionsin an embodiment of the present disclosure and may be changed byintentions, practices or the like of users or operators. Therefore, thedefinitions thereof should be construed based on the contents throughoutthe specification. A term used for identifying a connection node used inthe following description, a term referring to network entities, a termreferring to messages, a term referring to an interface between networkobjects, a term referring to various identification information, or thelike are illustrated for convenience of explanation. Accordingly, thepresent disclosure is not limited to terms to be described below andother terms indicating objects having the equivalent technical meaningmay be used.

Hereafter, for convenience of explanation, the present disclosure usesterms and names defined in the 3GPP LTE or terms and names modifiedbased on the terms and names. However, the present disclosure is notlimited to the terms and names but may also be identically applied tothe system according to other standards.

An embodiment of the present disclosure relates to a mobilecommunication system, and more particularly, to a method and apparatusfor selecting, by a pedestrian terminal, a resource pool in an LTEterminal supporting communication (vehicle-to-pedestrian, hereinafterreferred to as V2P) between a vehicle and a pedestrian terminal.However, the proposed contents may be applied to thevehicle-to-everything (V2X) communication technology as well as the V2Pcommunication.

A vehicle-to-everything (V2X) refers to a communication technologythrough a vehicle and all interfaces and examples thereof may include avehicle-to-vehicle (V2V), vehicle-to-infra-structure (V2I), avehicle-to-pedestrian (V2P), and the like according to the form thereofand the component forming the communication. The V2P basically dependson a structure and an operation principle of Rel-12 device-to-device(D2D). Like the D2D, even the V2P transmits/receives data between avehicle terminal and a pedestrian portable terminal (hereinafter,interchangeably used with a pedestrian UE (P-UE)), but in the cellsupporting the V2P, more terminals receives a service compared to theD2D receives, thereby reducing a waste of radio resources. Moreparticularly, in the case of mode 3 in which a base station assigns andmanages resources for the V2P, if a RRC-connected terminal has data tobe transmitted to another terminal, the data may be transmitted to thebase station using the RRC message or the MAC control element(hereinafter, referred to as CE). Here, as the RRC message,SidelinkUElnformation, UEAssistancelnformation message may be used.Meanwhile, the MAC CE may be, for example, a buffer status report MAC CEin a new format (including indicator that notifies at least a bufferstatus report for at least V2P communication and information on a sizeof data that are buffered for D2D communication). The detailed formatand content of the buffer status report used in the 3GPP refer to 3GPPstandard TS36.321 “S-UTRA MAC Protocol Specification”. The base stationreceiving the V2P communication request signals additionalconfiguration/setting information (V2V resource block assignmentinformation, modulation and coding (MCS), and timing advance (TA)) orV2V communication permission indicator for the V2V communication to theterminal, such that the terminal may performpermission/control/management to perform the V2V communication. Inaddition, sidelink (SL) communication in the V2P, that is, thedevice-to-device communication is operated based on a transmissionresource defined in the D2D. As described above, since more vehicleterminals will be serviced in the cell supporting the V2P than in theD2D, there is a need to efficiently manage transmission resources.

In addition, the most important consideration in V2P is reduction ofpower consumption of the pedestrian terminal. Unlike other terminalsused in V2X communication, the pedestrian portable terminal is greatlyrestricted in power consumption. For this purpose, unlike otherterminals of the V2X, a special power reducing technique for thepedestrian portable terminal is required. For this purpose, the use of aresource selection (a method for sensing scheduling assignment (SA) anddata resources used by neighboring terminals and transmitting themthrough an empty resource) based on sensing used in an existing vehicleterminal is limited. The resource selection operation based on theexisting sensing needs to detect the resource pool for a minimum of 1second and decode the SA, resulting in consuming much power. Instead, arandom resource selection technique that has been used in the existingRel-12 D2D may be used. In addition, a resource selection may be appliedthrough partial sensing, which is a modification of the sensingoperation of the related art. The partial sensing operation is a methodfor reducing power consumption by sensing a resource pool for more thanone second and reducing a procedure of decoding SA to a short intervalof about 100 ms. For example, the pedestrian portable terminal may useeither of operations of the random resource selection or the resourceselection through the partial sensing, or both of them.

According to an embodiment of the present disclosure, for the pedestrianportable terminal having sidelink Rx capability, as the random resourceselection and the resource selection through the partial sensing isefficiently selected, the conditions of reducing power consumption andincreasing transmission stability for high priority packets are defined.

FIG. 9A is a diagram illustrating a structure of an LTE system accordingto an embodiment of the present disclosure.

Referring to FIG. 9A, the wireless communication system is configured toinclude a plurality of base stations (eNB) 9 a-05, 9 a-10, 9 a-15, and 9a-20, a mobility management entity (MME) 9 a-25, and a serving-gateway(S-GW) 9 a-30. A user equipment 9 a-35 is connected to the externalnetwork through the base stations 9 a-05 to 9 a-20 and the S-GW 9 a-30.The base stations 9 a-05 to 9 a-20 are access nodes of a cellularnetwork and provides a radio access to the terminals that are connectedto the network. For example, in order to serve traffic of users, thebase stations 9 a-05 to 9 a-20 collect and schedule state information,such as a buffer state, an available transmit power state, and a channelstate of the UEs to support the connection between the terminals and thecore network (CN). The MME 9 a-25 is an apparatus for performing variouscontrol functions as well as the mobility management function for theterminal and is connected to a plurality of base stations, and the S-GW9 a-30 is an apparatus for providing a data bearer. Further, the MME andthe S-GWs 9 a-25 and 9 a-30 may further perform authentication, bearermanagement, and the like, on the terminal connected to the network andmay process packets that are to be received from the base stations 9a-05 to 9 a-20 and are to be transmitted to the base stations 9 a-05 to9 a-20.

FIG. 9B is a diagram illustrating V2P communication according to anembodiment of the present disclosure.

Referring to FIG. 9B, an example of performing the V2P communication inthe cellular system is illustrated.

Referring to FIG. 9B, the base station 9 b-01 manages at least onevehicle terminal 9 b-03 and the pedestrian portable terminal 9 b-04located in the cell 9 b-02. For example, the vehicle terminal 9 b-03performs cellular communication using a link 9 b-06 between the basestation 9 b-01 and the vehicle terminal-base station, and the pedestrianportable terminal 9 b-04 uses the base station 9 b-01 and a link 9 b-07between the pedestrian portable terminal and the base station to performthe cellular communication. If the vehicle terminal 9 b-03 and thepedestrian portable terminal 9 b-04 are capable of the V2Pcommunication, the vehicle terminal 9 b-03 and the pedestrian portableterminal 9 b-04 may directly transmit and receive information using thelink 9 b-05 without passing through the base station 9 b-01. The numberof terminals receiving the V2P service in one cell may be many and therelationship between the base station 9 b-01 and the terminals 9 b-03and 9 b-04 as described above may be extended and applied.

FIG. 9C is a diagram illustrating a procedure of a random resourceselection of a V2P terminal operated in mode 3 according to anembodiment of the present disclosure.

Referring to FIG. 9C, as described above, in the V2P communication, thebase station 9 c-03 allocates a resource pool for the random resourceselection and a pool for resource selection based on the partial sensingfor the pedestrian portable terminal 9 c-01. However, in order for theportable terminal 9 c-01 to perform the partial sensing operation, theside link reception capability is required. For example, since theportable terminal 9 c-01 that does not have the side link receptioncapability exists in the cell, the base station will provide theresource pool for at least one random resource selection. The portableterminal 9 c-01 that is camping on in operation 9 c-05 receives the SIB21 from the base station 9 c-03 in operation 9 c-10. The systeminformation includes resource pool information for transmission andreception, configuration information for sensing operation, informationfor setting synchronization, and the like. If the portable terminal 9c-01 generates the data traffic for the P2V in operation 9 c-15, itperforms the RRC connection with the base station in operation 9 c-20.The above RRC connection process may be performed before the datatraffic is generated in operation 9 c-15. The portable terminal 9 c-01requests a transmission resource capable of P2V communication with othervehicle terminals 9 c-02 to the base station in operation 9 c-25. Atthis time, the portable terminal 9 c-01 may request the base stationusing the RRC message or the MAC CE. Here, as the RRC message,SidelinkUElnformation, UEAssistancelnformation message may be used.Meanwhile, the MAC CE may be, for example, a buffer status report MAC CEin a new format (including indicator that notifies at least a bufferstatus report for at least V2P communication and information on a sizeof data that are buffered for D2D communication). The base station 9c-03 allocates a P2V transmission resource to the portable terminal 9c-01 through a dedicated RRC message in operation 9 c-30. The messagemay be included in the RRCConnectionReconfiguration message. Theportable terminal 9 c-01 randomly selects the resource in operation 9c-35 in the time/frequency domain from the resources indicated by thebase station 9 c-03 and transmits the data to the vehicle terminal 9c-02 in operation 9 c-40.

FIG. 9D is a diagram illustrating a procedure of a random resourceselection of a V2P terminal operated in mode 4 according to anembodiment of the present disclosure.

Referring to FIG. 9D, a mode 4 operation is different from mode 3 inwhich the base station 9 d-03 is directly involved in the resourceallocation in that the portable terminal 9 d-01 autonomously selects aresource based on the resource pool of system information received inadvance and transmits data. In the V2P communication, the base station 9d-03 allocates a resource pool for the random resource selection and apool for resource selection based on the partial sensing for thepedestrian portable terminal 9 d-01. However, in order for the portableterminal 9 d-01 to perform the partial sensing operation, the side linkreception capability is required. For example, since the portableterminal 9 d-01 that does not have the side link reception capabilityexists in the cell, the base station will provide the resource pool forat least one random resource selection. The portable terminal 9 d-01that is camping on in operation 9 c-05 receives the SIB 21 from the basestation 9 d-03 in operation 9 d-10. The system information includesresource pool information for transmission and reception, configurationinformation for sensing operation, information for settingsynchronization, and the like. If the portable terminal 9 d-01 generatesthe data traffic for the P2V in operation 9 d-15, the portable terminal9 d-01 selects the pool from which the random resource can be selectedamong the resource pools received from the base station 9 d-03 throughthe system information and randomly selects the resource in thetime/frequency domain in operation 9 d-20 and transmits the data to thevehicle terminal 9 d-02 at random in operation 9 d-25.

FIG. 9E is a diagram illustrating a partial sensing operation in V2Paccording to an embodiment of the present disclosure.

Referring to FIG. 9E, as described above, when operated in mode 4 ofV2V, the resource selection based on the sensing may be performed.First, all the resources are considered to be usable, and the mode 4terminal excludes resources already in use through the sensing and SAdecoding for the resource pool. Finally, after the sensing operationends, the terminal selects the remaining resources and transmits thedata through the selected resources. However, in the case of apedestrian portable terminal, since there is a great concern about powerconsumption of the operation, the random resource selection is used andthe simplified sensing operation, that is, the partial sensing operationmay be further performed. The P2V portable terminal repeats theoperation of sensing the surrounding resources only for a while at aperiod of 100 ms during a corresponding sensing period (9 e-05) withoutusing a sensing window of 1 second used in the existing sensingoperation. Here, the sensing window 9 e-15 may have a small size ofabout 100 ms (9 e-10). The resource is selected in operation 9 e-20 inorder to reflect the sensing result measured ten times during thesensing period (9 e-05). For example, as a result of the sensing, anempty resource is selected except the resources occupied by otherterminals. In addition, in operation 9 e-25, the SA and the related dataare transmitted through the resources determined through the selectionwindow. The partial sensing operation may be performed only for the P2Vportable terminal having the sidelink Rx capability.

FIG. 9F is a diagram illustrating a method of determining a resourcepool of a V2P terminal in a base station control mode according to a9-1-th embodiment of the present disclosure.

Referring to FIG. 9F, as described above, the portable terminal for theP2V may use the random resource selection and the partial sensing basedon the partial sensor, which depends on the side link receptioncapability of the terminal and the configuration of the network. Forexample, if the terminal supports both operations, whether or not theresource pool is set in the network affects the operation. In addition,for the P2V mobile terminal, the base station may provide the pool forthe random resource selection (hereinafter referred to as R-Pool) andthe resource pool (hereinafter referred to as PS-Pool) for the partialsensing for the specific portable terminal. Here, the R-Pool may overlapwith the PS-Pool, which is an implementation issue of the network. Inthe 9-1-th embodiment, the resource selection operation of the P2Vportable terminal when the CBR measurement and report can be performedin the R-Pool, and the operation of the base station control mode willbe described in detail below. Herein, the base station control modereports a CBR measurement value related to the congestion control to thebase station, and determines the operation of the terminal (resourcepool selection method of the terminal) by comparing the reported CBRmeasurement value with a predetermined threshold value of the basestation. On the other hand, the terminal autonomous mode is a method (aresource pool selection method of the terminal) for determining, aterminal, an operation by comparing the CBR measurement value with thepredetermined threshold without reporting the CBR measurement value tothe base station. More particularly, the base station control mode isapplicable to the V2X terminal of mode 3 and the mode 4 terminal of RRCconnection state.

Meanwhile, the PS-Pool related contents described below may be similarlyapplied to the sensing based operation process of the V2X communication.

The portable terminal 9 f-01 that is camping on in operation 9 f-05receives the SIB 21 from the base station 9 f-03 in operation 9 f-10.The system information includes resource pool information fortransmission and reception, configuration information for sensingoperation, information for setting synchronization, parameters(indicator indicating a periodic report and an event generation report,a threshold value indicating a congestion degree, a threshold value forclassification depending on PPPP), and the like. If the portableterminal 9 f-01 generates the data traffic for the P2V in operation 9f-15, it performs the RRC connection with the base station in operation9 f-20. The above RRC connection process may be performed before thedata traffic is generated in operation 9 f-15. The portable terminal 9f-01 requests a transmission resource capable of P2V communication withother vehicle terminals 9 f-02 to the base station in operation 9 f-25.At this time, the portable terminal may request a resource to the basestation 9 f-03 using the RRC message or the MAC CE. Here, as the RRCmessage, SidelinkUEInformation, UEAssistancelnformation message may beused. Meanwhile, the MAC CE may be, for example, a buffer status reportMAC CE in a new format (including indicator that notifies at least abuffer status report for at least V2P communication and information on asize of data that are buffered for D2D communication). The base station9 f-03 checks the side link reception capability of the portableterminal 9 f-01 in operation 9 f-30 and allocates the transmissionresources to the P2V portable terminal 9 f-01 through the dedicated RRCmessage. The message is included in the RRCConnectionReconfigurationmessage, and may instruct the R-Pool and the PS-Pool to the P2V mobileterminal 9 f-01. For example, in the message, the base station 9 f-03may instruct the resource allocation for the random resource selectionand the partial sensing operation according to the capability of the P2Vportable terminal 9 f-01 in operation 9 f-35. In the operation the basestation may indicate one of the random resource selection and thepartial sensing operation and may indicate both. In operation 9 f-40,the P2V portable terminal 9 f-01 detects the R-Pool and then measuresthe CBR. In operation 9 f-45, the measurement result is transmitted tothe base station 9 f-03, and the periodic report or the event generationreport is based on the method set by the base station. In operation 9f-50, the base station 9 f-03 compares the CBR measurement valuereported by the portable terminal 9 f-01 with the predeterminedthreshold value, and then determines the congestion of the R-Pool. Inaddition, the use of the conditional PS-Pool is defined based on mappingwith a plurality of thresholds associated with the packet priority(Prose per-packet priority (PPPP)) of the portable terminal 9 f-01.

In the following Table 9-1, an example in which four threshold valuescorresponding to eight PPPPs are set will be described.

TABLE 9-1 Condition Action CBR value < R-Pool is used Thres_CBR Thres1<= CBR PS-Pool is used for higher 2 PPPP of P-UE's packet, value <Thres2 R-Pool is used for the rest of P-UE's packet Thres2 <= CBRPS-Pool is used for higher 4 PPPP of P-UE's packet, value < Thres3R-Pool is used for the rest of P-UE's packet Thres3 <= CBR PS-Pool isused for higher 6 PPPP of P-UE's packet, value < Thres4 R-Pool is usedfor the rest of P-UE's packet Thres4 <= CBR PS-Pool is used for allP-UE's packet value

Here, Thres1<Thres2<Thres3<Thres4, and Thres CBR may be equal to or lessthan Thres1. The operation is applied when the P2V portable terminal 9f-01 may be operated in both modes (random resource selection andpartial sensing operation), and the operation may be performed in bothof the case where the R-Pool overlaps with the PS-Pool and is defined asa different pool. For example, both of the change from the R-Pool to thePS-Pool or the change in the use method may be considered. Here, thethreshold value mapped to the PPPP may have a value from 1 to 8.

In operation 9 f-55, the base station 9 f-03 instructs the operation ofthe portable terminal 9 f-01 determined based on the mapping ruledescribed in Table 9-1. In operation 9 f-60, the portable terminal 9f-01 performs the random resource selection and the partial sensingoperation according to the instruction received from the base station.The data is transmitted to the vehicle terminal 9 f-02 through theselected resource in operation 9 f-65.

FIG. 9G is a diagram illustrating a method of determining a resourcepool of a V2P terminal operated in a terminal-autonomous mode accordingto a 9-1-th embodiment of the present disclosure.

Referring to FIG. 9G, the base station control mode reports a CBRmeasurement value related to the congestion control to the base station,and determines the operation of the terminal (resource pool selectionmethod of the terminal) by comparing the reported CBR measurement valuewith a predetermined threshold value of the base station. On the otherhand, the terminal autonomous mode is a method (a resource poolselection method of the terminal) for determining, a terminal, anoperation by comparing the CBR measurement value with the predeterminedthreshold without reporting the CBR measurement value to the basestation. More particularly, the terminal autonomous mode can be appliedto the mode 4 in V2X communication, and may also be applied to the casewhere the mode 3 terminal is in the IDLE state or out-of-coverage (OOC).

The portable terminal 9 g-01 which is camping on in operation 9 g-05receives the SIB 21 from the base station 9 g-03 in operation 9 g-10.The system information includes resource pool information fortransmission and reception, configuration information for sensingoperation, information for setting synchronization, parameters(indicator indicating a periodic report and an event generation report,a threshold value indicating a congestion degree, a threshold value forclassification depending on PPPP), and the like If the portable terminal9 g-01 generates the data traffic for the P2V in operation 9 g-15, itperforms the RRC connection with the base station in operation 9 g-20.The above RRC connection process may be performed before the datatraffic is generated in operation 9 g-15. The portable terminal 9 g-01requests a transmission resource capable of P2V communication with othervehicle terminals 9 g-02 to the base station 9 g-03 in operation 9 g-25.At this time, the portable terminal may request a resource to the basestation 9 g-03 using the RRC message or the MAC CE. Here, as the RRCmessage, SidelinkUEInformation, UEAssistancelnformation message may beused. Meanwhile, the MAC CE may be, for example, a buffer status reportMAC CE in a new format (including indicator that notifies at least abuffer status report for at least V2P communication and information on asize of data that are buffered for D2D communication). The base station9 g-03 checks the side link reception capability of the portableterminal 9 g-01 and allocates the transmission resources to the P2Vportable terminal 9 g-01 through the dedicated RRC message in operation9 g-30. The message is included in the RRCConnectionReconfigurationmessage, and may instruct the R-Pool and the PS-Pool to the P2V mobileterminal 9 g-01. The operations 9 g-20 to 9 g-30 may not be performedfor the mode 4 terminal.

In operation 9 g-35, the P2V mobile terminal 9 g-01 measures the CBR forchecking the congestion degree in the P-Pool after checking the sidelink reception capability by itself. In operation 9 g-40, the portableterminal 9 g-01 compares the measured CBR measurement value with thesystem information or the predetermined threshold value from the basestation 9 g-01, and then determines the congestion of the R-Pool. Inaddition, the use of the conditional PS-Pool is defined based on mappingwith a plurality of thresholds associated with the packet priority(PPPP) of the portable terminal 9 g-01

In the following Table 9-2, an example in which four threshold valuescorresponding to eight PPPPs are set will be described.

TABLE 9-2 Condition Action CBR R-Pool is used value < Thres_CBR Thres1<= CBR PS-Pool is used for higher 2 PPPP of P-UE's packet, value <Thres2 R-Pool is used for the rest of P-UE's packet Thres2 <= CBRPS-Pool is used for higher 4 PPPP of P-UE's packet, value < Thres3R-Pool is used for the rest of P-UE's packet Thres3 <= CBR PS-Pool isused for higher 6 PPPP of P-UE's packet, value < Thres4 R-Pool is usedfor the rest of P-UE's packet Thres4 <= CBR PS-Pool is used for allP-UE's packet value

Here, Thres1<Thres2<Thres3<Thres4, and Thres CBR may be equal to or lessthan Thres1. The operation is applied when the P2V portable terminal 9f-01 may be operated in both modes (random resource selection andpartial sensing operation), and the operation may be performed in bothof the case where the R-Pool overlaps with the PS-Pool and is defined asdifferent pools. For example, both of the change from the R-Pool to thePS-Pool or the change in the use method may be considered. Here, thethreshold value mapped to the PPPP may have a value from 1 to 8.

In operation 9 g-45, the portable terminal 9 g-01 transmits data to thevehicle terminal 9 g-02 through the selected resource.

FIG. 9H is a diagram illustrating a method of determining a resourcepool of a V2P terminal operated in a base station control mode accordingto a 9-2-th embodiment of the present disclosure.

Referring to FIG. 9H, in the 9-2-th embodiment, the resource selectionoperation of the P2V portable terminal when the CBR measurement andreport cannot be performed in the R-Pool, and the operation of the basestation control mode will be described in detail below. Herein, the basestation control mode reports a CBR measurement value related to thecongestion control to the base station, and determines the operation ofthe terminal (resource pool selection method of the terminal) bycomparing the reported CBR measurement value with a predeterminedthreshold value of the base station. On the other hand, the terminalautonomous mode is a method (a resource pool selection method of theterminal) for determining, a terminal, an operation by comparing the CBRmeasurement value with the predetermined threshold without reporting theCBR measurement value to the base station. More particularly, the basestation control mode is applicable to the V2X terminal of mode 3 and themode 4 terminal of RRC connection state.

The portable terminal 9 h-01 that is camping on in operation 9 h-05receives the SIB 21 from the base station 9 h-03 in operation 9 h-10.The system information includes resource pool information fortransmission and reception, configuration information for sensingoperation, information for setting synchronization, parameters(indicator indicating a periodic report and an event generation report,a threshold value indicating a congestion degree, a threshold value forclassification depending on PPPP), and the like In addition, a set ofparameters (MCS, PRB count, power control, and the like) in a physicalarea depending on the congestion degree may also be included in plural.For example, it may be used to adjust the parameter values of thephysical area according to the congestion degree of the PS-Pool. Forexample, it is used in the same method as Table 9-3 below

TABLE 9-3 Condition Action Non-congestion in PS-Pool Set A oftransmission parameter Congestion in PS-Pool Multiple sets (B, C, . . .) of transmission parameter

If the portable terminal 9 h-01 generates the data traffic for the P2Vin operation 9 h-15, it performs the RRC connection with the basestation in operation 9 h-20. The above RRC connection process may beperformed before the data traffic is generated in operation 9 h-15. Theportable terminal 9 h-01 requests a transmission resource capable of P2Vcommunication with other vehicle terminals 9 h-02 to the base station 9h-03 in operation 9 h-25. At this time, the portable terminal mayrequest a resource to the base station 9 h-03 using the RRC message orthe MAC CE. Here, as the RRC message, SidelinkUElnformation,UEAssistancelnformation message may be used. Meanwhile, the MAC CE maybe, for example, a buffer status report MAC CE in a new format(including indicator that notifies at least a buffer status report forat least V2P communication and information on a size of data that arebuffered for D2D communication). The base station 9 h-03 checks the sidelink reception capability of the portable terminal 9 h-01 in operation 9h-30 and allocates the transmission resources to the P2V portableterminal 9 h-01 through the dedicated RRC message in operation 9 h-35.The message is included in the RRCConnectionReconfiguration message, andmay instruct the R-Pool and the PS-Pool to the P2V mobile terminal 9h-01. For example, in the message, the base station 9 h-03 may instructthe resource allocation for the random resource selection and thepartial sensing operation according to the capability of the P2Vportable terminal 9 h-01 in operation 9 h-35. The base station 9 h-03may indicate one of the random resource selection and the partialsensing operation and may indicate both. In the present embodiment,since it is assumed that the sensing of the R-Pool and the CBRmeasurement is impossible, only the case where the base station 9 h-03explicitly specifies the resource selection operation of the portableterminal 9 h-01 is handled. For example, if the base station 9 h-03instructs the random resource selection, the portable terminal 9 h-01performs the random resource selection, and performs the followingoperation if instructing the partial sensing operation. As the methodfor determining, by a base station 9H-03, an operation of a portableterminal 9 h-01 may be performed according to the implementation or thesatisfaction of the predetermined event.

In operation 9 h-40, the P2V portable terminal 9 h-01 detects thePS-Pool and then measures the CBR. In operation 9 h-45, the measurementresult is transmitted to the base station 9 h-03, and the periodicreport or the event generation report is based on the method set by thebase station. In operation 9 h-50, the base station 9 h-03 compares theCBR measurement value reported by the portable terminal 9 h-01 with thepredetermined threshold value, and then determines the congestion of thePS-Pool. In addition, the use of the conditional PS-Pool is definedbased on mapping with a plurality of thresholds associated with thepacket priority (PPPP) of the portable terminal 9 h-01 For example, a Txparameter set for the partial sensing operation and the congestioncontrol is determined based on the mapping rule of the packet priorityand the predetermined threshold values, and the terminal is instructedin operation 9 h-55.

In the following Table 9-4, an example in which four threshold valuescorresponding to eight PPPPs are set will be described. In this example,the case where three parameter sets (Set A, B, C) for transmission ofthe physical layer are set to be three (set A, B, and C) is shown.

TABLE 9-4 Steps Condition Action Step 1 CBR value > Change the Parameterset Thres_CBR (From Parameter set A to Parameter set B) Change R-Pool toPS-Pool Step 2 Thres1 <= CBR Parameter set C for higher 2 PPPP of value< Thres2 P-UE's packet, Parameter set B used for the rest of P-UE'spacket Thres2 <= CBR Parameter set C for higher 4 PPPP of value < Thres3P-UE's packet, Parameter set B used for the rest of P-UE's packet Thres3<= CBR Parameter set C for higher 6 PPPP of value < Thres4 P-UE'spacket, Parameter set B used for the rest of P-UE's packet Thres4 <= CBRvalue Parameter set C for all P-UE's packet,

Here, Thres1<Thres2<Thres3<Thres4, and Thres CBR may be equal to or lessthan Thres1. In addition, a parameter set A is provided as a default andparameter sets B and C may be used depending on the congestion degree.The transmission-related parameters of the physical layer included inthe parameter set B are set to be a smaller value so as to reduce thecongestion, as compared with those belonging to the parameter A. Forexample, MCS A, No PRB A, and Power A of the parameter set A aredetermined to be larger than MCS B, No PRB B, and Power B of theparameter set B. This applies similarly to the relationship betweenparameter sets B and C. In addition, even if the number of parametersets increases, the transmission parameter values configured from theviewpoint may be set. In addition, the base station may instruct theportable terminal using the R-Pool in operation 1 to be changed to thePS-pool while changing the parameter set.

This operation is applied when the P2V mobile terminal 9 h-01 isoperated as the partial sensing operation, and may be applied to bothwhen the PS-Pool overlaps with the R-Pool and when the PS-Pool isdefined as different pools. For example, both of the change from theR-Pool to the PS-Pool or the change in the use method may be considered.Here, the threshold value mapped to the PPPP may have a value from 1 to8.

In operation 9 h-60, the portable terminal 9 h-01 determines thetransmission parameter set and performs the partial sensing operation,depending on the packet priority according to the instruction receivedfrom the base station. The data is transmitted to the vehicle terminal 9f-02 through the selected resource in operation 9 h-65.

FIG. 9I is a diagram illustrating a method of determining a resourcepool of a V2P terminal operated in a terminal autonomous mode accordingto a 9-2-th embodiment of the present disclosure.

Referring to FIG. 9I, the base station control mode reports a CBRmeasurement value related to the congestion control to the base station,and determines the operation of the terminal (resource pool selectionmethod of the terminal) by comparing the reported CBR measurement valuewith a predetermined threshold value of the base station. On the otherhand, the terminal autonomous mode is a method (a resource poolselection method of the terminal) for determining, a terminal, anoperation by comparing the CBR measurement value with the predeterminedthreshold without reporting the CBR measurement value to the basestation. More particularly, the terminal autonomous mode can be appliedto the mode 4 in V2X communication, and may also be applied to the casewhere the mode 3 terminal is in the IDLE state or the out-of-coverage(OOC).

The portable terminal 9 i-01 that is camping on in operation 9 i-05receives the SIB 21 from the base station 9 i-03 in operation 9 i-10.The system information includes resource pool information fortransmission and reception, configuration information for sensingoperation, information for setting synchronization, parameters(indicator indicating a periodic report and an event generation report,a threshold value indicating a congestion degree, a threshold value forclassification depending on PPPP), and the like In addition, a set ofparameters (MC S, PRB count, power control, and the like) in a physicalarea depending on the congestion degree may also be included in plural.For example, it may be used to adjust the parameter values of thephysical area according to the congestion degree of the PS-Pool. Forexample, it is used in the same method as Table 9-5 below

TABLE 9-5 Condition Action Non-congestion in PS-Pool Set A oftransmission parameter Congestion in PS-Pool Multiple sets (B, C, . . .) of transmission parameter

If the portable terminal 9 i-01 generates the data traffic for the P2V(9 i-15), it performs the RRC connection with the base station inoperation 9 i-20. The above RRC connection process may be performedbefore the data traffic is generated in operation 9 i-15. The portableterminal 9 i-01 requests a transmission resource capable of P2Vcommunication with other vehicle terminals 9 i-02 to the base station 9i-03 in operation 9 i-25. At this time, the portable terminal mayrequest a resource to the base station 9 i-03 using the RRC message orthe MAC CE. Here, as the RRC message, SidelinkUEInformation,UEAssistanceInformation message may be used. Meanwhile, the MAC CE maybe, for example, a buffer status report MAC CE in a new format(including indicator that notifies at least a buffer status report forat least V2P communication and information on a size of data that arebuffered for D2D communication). The base station 9 i-03 checks the sidelink reception capability of the portable terminal 9 i-01 and allocatesthe transmission resources to the P2V portable terminal 9 i-01 throughthe dedicated RRC message in operation 9 i-30. The message is includedin the RRCConnectionReconfiguration message, and may instruct the R-Pooland the PS-Pool to the P2V mobile terminal 9 i-01. The operations 9 i-20to 9 i-30 may not be performed for the mode 4 terminal.

In operation 9 i-35, the P2V mobile terminal 9 i-01 measures the CBR forchecking the congestion degree in the PS-Pool after checking the sidelink reception capability by itself. The portable terminal determinesthe resource pool and the operation according to the setting in the basestation included in the system information. If only the R-Pool exists,the random resource selection is performed. In addition, when the R-Pooland the PS-Pool are simultaneously instructed, the random resourceselection is performed when the capability of the terminal is not ableto be partially detected, and the PS-Pool is used when the partialsensing is possible.

In operation 9 i-40, the portable terminal 9 i-01 compares the measuredCBR measurement value with the system information or the predeterminedthreshold value from the base station 9 i-01, and then determines thecongestion of the PS-Pool. In addition, the use of the conditionalPS-Pool is defined based on mapping with a plurality of thresholdsassociated with the packet priority (PPPP) of the portable terminal 9i-01 For example, the portable terminal determines the Tx parameter setfor the partial sensing operation and the congestion control based onthe mapping rule of the packet priority and the predetermined thresholdvalues in operation 9 i-45.

In the following Table 9-6, an example in which four threshold valuescorresponding to eight PPPPs are set will be described. In this example,the case where three parameter sets (Set A, B, C) for transmission ofthe physical layer are set to be three (set A, B, and C) is shown.

TABLE 9-6 Steps Condition Action Step 1 CBR value > Change the Parameterset Thres_CBR (From Parameter set A to Parameter set B) Change R-Pool toPS-Pool Step 2 Thres1 <= CBR Parameter set C for higher 2 PPPP of value< Thres2 P-UE's packet, Parameter set B used for the rest of P-UE'spacket Thres2 <= CBR Parameter set C for higher 4 PPPP of value < Thres3P-UE's packet, Parameter set B used for the rest of P-UE's packet Thres3<= CBR Parameter set C for higher 6 PPPP of value < Thres4 P-UE'spacket, Parameter set B used for the rest of P-UE's packet Thres4 <= CBRvalue Parameter set C for all P-UE's packet,

Here, Thres1<Thres2<Thres3<Thres4, and Thres CBR may be equal to or lessthan Thres1. In addition, a parameter set A is provided as a default andparameter sets B and C may be used depending on the congestion degree.The transmission-related parameters of the physical layer included inthe parameter set B are set to be a smaller value so as to reduce thecongestion, as compared with those belonging to the parameter A. Forexample, MCS A, No PRB A, and Power A of the parameter set A aredetermined to be larger than MCS B, No PRB B, and Power B of theparameter set B. This applies similarly to the relationship betweenparameter sets B and C. In addition, even if the number of parametersets increases, the transmission parameter values configured from theviewpoint may be set. In addition, the base station may instruct theportable terminal using the R-Pool in operation 1 to be changed to thePS-pool while changing the parameter set.

This operation is applied when the P2V mobile terminal 9 i-01 isoperated as the partial sensing operation, and may be applied to bothwhen the PS-Pool overlaps with the R-Pool and when the PS-Pool isdefined as different pools. For example, both of the change from theR-Pool to the PS-Pool or the change in the use method may be considered.Here, the threshold value mapped to the PPPP may have a value from 1 to8.

In operation 9 i-40, the portable terminal 9 i-01 determines thetransmission parameter set and performs the partial sensing operation,depending on the packet priority according to the instruction receivedfrom the base station. The data is transmitted to the vehicle terminal 9i-02 through the selected resource in operation 9 i-45.

FIG. 9J is a diagram illustrating an operation of a terminal accordingto a 9-1-th embodiment of the present disclosure.

Referring to FIG. 9J, in the 9-1-th embodiment, the operation of theterminal that is operated in the base station control mode is asfollows.

In operation 9 j-05, the P2V portable terminal receives the systeminformation.

The system information includes the R-Pool for the random resourceselection and the PS-Pool information for the partial sensing, theconfiguration information for the sensing operation, the information forsetting synchronization, the information for the CBR measurement and thereporting (period, threshold value, threshold for classificationaccording to PPPP, and the like), and a set of parameters (MCS, thenumber of PRBs, power control, and the like) of a plurality of physicalareas.

Determining the operation according to the mode of the terminal

The mode 3 portable terminal and the mode 4 portable terminal in theRRC-connected state is operated in the base station control mode inoperations 9 j-10 to 9 j-20.

For the mode 4 and the mode 3 in the IDLE state, the terminal isoperated in the autonomous mode. In this case, instead of the operations9 j-10 to 9 j-20, the resource pool provided from the received systeminformation is used.

Determining a method for using, by a terminal, a resource pool andtransmitting data according to side link reception capability inoperation 9 j-25.

If the side link reception capability of the UE is not determined inoperation 9 j-25, data is transmitted using random resource selection ondedicated R-Pool in operation 9 j-30. In the case of the base stationcontrol mode, it is possible to determine the resource pool and theoperation of the portable terminal by receiving the side link receptioncapability of the terminal and instruct, by the base station, theresource pool in advance in operation 9 j-35 and determine, by theterminal itself, the operation of the portable terminal. When theterminal is operated in the autonomous mode, the terminal itselfdetermines the operation according to the side link reception capabilityof the portable terminal.

Measuring the CBR for the R-Pool for the terminal performing theresource selection operation through the partial sensing in operation 9j-40.

In the base station control mode, the terminal may transmit the CBRmeasurement value to the base station in operation 9 j-45. If theterminal operates in autonomous mode, the terminal does not transmit theCBR measurement value to the base station.

Determining the method for using a resource pool and transmitting databased on a comparison between the CBR value and the preset thresholdvalue

In the base station control mode, the base station compares the CBRmeasurement value received from the terminal with the predeterminedthreshold value and determines the transmission method according to thepredetermined mapping rule in operation 9 j-50. On the other hand, ifthe terminal is operated in an autonomous mode, the terminal comparesthe calculated CBR measurement value with the threshold value receivedas the system information and determines the transmission methodaccording to the predetermined mapping rule. The mapping rule may beassociated with the selection and operation of resource pools accordingto the packet priority in operation 9 j-60.

Transmitting the side link data after the random resource selection inoperation 9 j-55.

Transmitting the side link data after the resource selection based onthe partial sensing in operation 9 j-65.

FIG. 9K is a diagram illustrating an operation of a terminal accordingto a 9-2-th embodiment of the present disclosure.

Referring to FIG. 9K, in the 9-2-th embodiment, the operation of theterminal that is operated in the base station control mode is asfollows.

In operation 9 j-05, the P2V portable terminal receives the systeminformation.

The system information includes the R-Pool for the random resourceselection and the PS-Pool information for the partial sensing, theconfiguration information for the sensing operation, the information forsetting synchronization, the information for the CBR measurement and thereporting (period, threshold value, threshold for classificationaccording to PPPP, and the like), and a set of parameters (MCS, thenumber of PRBs, power control, and the like) of a plurality of physicalareas.

Determining the operation according to the mode of the terminal

The mode 3 and mode 4 portable terminals in the RRC-connected state areoperated in the base station control mode in operations 9 j-10 to 9j-20.

For the mode 4 and the mode 3 in the IDLE state, the terminal isoperated in the autonomous mode. In this case, instead of the operations9 k-10 to 9 k-20, the resource pool provided from the received systeminformation is used.

Determining a method for using, by a terminal, a resource pool andtransmitting data according to side link reception capability inoperation 9 k-25.

If the side link reception capability of the UE is not determined inoperation 9 k-25, data is transmitted using random resource selection ondedicated R-Pool in operation 9 k-30. In the case of the base stationcontrol mode, it is possible to determine the resource pool and theoperation of the portable terminal by receiving the side link receptioncapability of the terminal and instruct, by the base station, theresource pool in advance in operation 9 k-35 and determine, by theterminal itself, the operation of the portable terminal. When theterminal is operated in the autonomous mode, the terminal itselfdetermines the operation according to the side link reception capabilityof the portable terminal.

Measuring the CBR for the PS-Pool for the terminal performing theresource selection operation through the partial sensing in operation 9k-40.

In the base station control mode, the terminal may transmit the CBRmeasurement value to the base station in operation 9 k-45. If theterminal operates in autonomous mode, the terminal does not transmit theCBR measurement value to the base station.

Determining the method for using a resource pool and transmitting databased on a comparison between the CBR value and the preset thresholdvalue

In the base station control mode, the base station compares the CBRmeasurement value received from the terminal with the predeterminedthreshold value and determines the transmission method according to thepredetermined mapping rule in operation 9 k-50. On the other hand, ifthe terminal is operated in an autonomous mode, the terminal comparesthe calculated CBR measurement value with the threshold value receivedas the system information and determines the transmission methodaccording to the predetermined mapping rule. Here, the mapping rule maybe associated with the selection and operation of resource poolsaccording to the packet priority. In addition, the mapping between theCBR measurement value and the transmission parameter set according tothe packet priority of the terminal is performed in operation 9 k-60.

Transmitting the side link data after the random resource selection inoperation 9 k-55.

Transmitting the side link data after the resource selection based onthe partial sensing in operation 9 k-65.

FIG. 9L is a block configuration diagram illustrating a terminalaccording to an embodiment of the present disclosure.

Referring to FIG. 9L, the terminal according to the embodiment of thepresent disclosure includes a transceiver 9 l-05, a controller 9 l-10, amultiplexer and demultiplexer 9 l-15, various upper layer processors 9l-20 and 9 l-25, and a control message processor 9 l-30.

The transceiver 9 l-05 receives data and a predetermined control signalthrough a forward channel of the serving cell and transmits the data andthe predetermined control signal through a the reverse channel. When aplurality of serving cells are configured, the transceiver 9 l-05transmits and receives data and a control signal through the pluralityof carriers. The multiplexer and demultiplexer 9 l-15 serves tomultiplex data generated from the upper layer processors 9 l-20 and 9l-25 or the control message processor 9 l-30 or demultiplex datareceived by the transceiver 9 l-05 and transmit the data to theappropriate upper layer processors 9 l-20 and 9 l-25 or the controlmessage processor 9 l-30. The control message processor 9 l-30 transmitsand receives a control message from the base station and takes necessaryactions. This includes the function of processing the RRC message andthe control messages, such as the MAC CE, and includes reporting of theCBR measurement value and receiving the RRC messages for the resourcepool and the operation of the terminal. The upper layer processors 9l-20 and 9 l-25 mean the DRB apparatus and may be configured for eachservice. The higher layer processors 9 l-20 and 9 l-25 process datagenerated from user services, such as a file transfer protocol (FTP) ora voice over internet protocol (VoIP) and transfer the processed data tothe multiplexer and demultiplexer 9 l-15 or process the data transferredfrom the multiplexer and demultiplexer 9 l-15 and transfer the processeddata to service application of the higher layer. The controller 9 l-10confirms scheduling commands, for example, reverse grants controlsreceived through the transceiver 9 l-05 to control the transceiver 9l-05 and the multiplexer and demultiplexer 9 l-15 to perform the reversetransmission by an appropriate transmission resource at an appropriatetime. Meanwhile, it is described above that the terminal is configuredof a plurality of blocks and each block performs different functions,which is only embodiment and therefore is not necessarily limitedthereto. For example, the controller 9 l-10 itself may also perform thefunction performed by the demultiplexer 9 l-15.

FIG. 9M is a block configuration diagram of a base station according toan embodiment of the present disclosure.

Referring to FIG. 9M, the base station apparatus includes a transceiver9 m-05, a controller 9 m-10, a multiplexer and demultiplexer 9 m-20, acontrol message processor 9 m-35, various upper layer processors 9 m-25and 9 m-30, and a scheduler 9 m-15.

The transceiver 9 m-05 transmits data and a predetermined control signalthrough a forward carrier and receives the data and the predeterminedcontrol signal through a reverse carrier. When a plurality of carriersare configured, the transceiver 9 m-05 transmits and receives the dataand the control signal through the plurality of carriers. Themultiplexer and demultiplexer 9 m-20 serves to multiplex data generatedfrom the upper layer processors 9 m-25 and 9 m-30 or the control messageprocessor-35 or demultiplex data received by the transceiver 9 m-25 andtransmit the data to the appropriate upper layer processors 9 m-30 and 9m-30 the control message processor 9 m-35, or the controller 9 m-10. Thecontroller 9 m-10 determines which of the resource pools received fromthe base station is used, and determines the random resource selectionoperation based on the configuration information and the resourceselection operation based on the partial sensing. The control messageprocessor 9 m-35 receives the instruction of the controller, generates amessage to be transmitted to the terminal, and transmits the generatedmessage to the lower layer. The upper layer processors 9 m-25 and 9 m-30may be configured for each terminal and each service and processes datagenerated from user services, such as FTP and VoIP and transmits theprocessed data to the multiplexer and demultiplexer 9 m-20 or processesdata transmitted from the multiplexer and demultiplexer 9 m-20 andtransmits the processed data to service applications of the upper layer.The scheduler 9 m-15 allocates a transmission resource to the terminalat appropriate timing based on the buffer status and the channel statusof the terminal, the active time of the terminal, and the like, andallows the transceiver to process a signal transmitted from the terminalor performs a process to transmit a signal to the terminal.

The embodiments of the present disclosure and the accompanying drawingshave proposed specific examples in order to easily describe the contentsof the present disclosure and assist in understanding the presentdisclosure and do not limit the scope of the present disclosure. It isobvious to those skilled in the art to which the present disclosurepertains that various modifications may be made without departing fromthe scope of the present disclosure, in addition to the embodimentsdisclosed herein.

In embodiments of the present disclosure, components included in thepresent disclosure are represented by a singular number or a pluralnumber according to the detailed embodiment as described above. However,the expressions of the singular number or the plural number are selectedto meet the situations proposed for convenience of explanation and thepresent disclosure is not limited to the single component or the pluralcomponents and even though the components are represented in plural, thecomponent may be configured in a singular number or even though thecomponents are represented in a singular number, the component may beconfigured in plural.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various changes in form and details may be made thereinwithout departing from the scope and spirit of the present disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A method for transmitting data by a transmittingdevice in a wireless communication system, the method comprising:receiving a radio link control (RLC) data unit from an upper layer;generating an RLC protocol data unit (PDU) including an RLC header, theRLC header including a segmentation information (SI) field indicatingwhether the RLC PDU includes a complete RLC data unit which is the RLCdata unit, a first segment of the RLC data unit, a middle segment of theRLC data unit or a last segment of the RLC data unit; and transmittingthe RLC PDU to a receiving device, wherein the RLC header furtherincludes a segment offset (SO) field, in case that the SI fieldindicates that the RLC PDU includes the middle segment of the RLC dataunit or the last segment of the RLC data unit, wherein the RLC headerdoes not include the SO field, in case that the SI field indicates thatthe RLC PDU includes the first segment of the RLC data unit or thecomplete RLC data unit, and wherein the SO field indicates a position ofa segment of the RLC data unit within the RLC data unit.
 2. The methodof claim 1, wherein the SI field indicates whether the SO field isincluded in the RLC header.
 3. The method of claim 1, wherein the SOfield indicates the position within the RLC data unit to which a firstbyte of the segment of the RLC data unit corresponds.
 4. The method ofclaim 1, wherein the method further comprises: generating another RLCPDU for a retransmission of the RLC data unit; and transmitting theanother RLC PDU to the receiving device, wherein an RLC header for theanother RLC PDU includes the SI field without the SO field, in case thatthe SI field indicates that the RLC PDU includes the first segment ofthe RLC data unit or the complete RLC data unit.
 5. The method of claim1, wherein the RLC header further includes a sequence number (SN) field,a data/control (D/C) field, and a polling bit (P) field, and wherein theRLC header does not include a re-segmentation flag (RF) field, a framinginformation (FI) field, a last segment flag (LSF) field and an extensionbit (E) field.
 6. A transmitting device for transmitting data in awireless communication system, the transmitting device comprising: atransceiver; and at least one processor configured to: receive a radiolink control (RLC) data unit from an upper layer, generate an RLCprotocol data unit (PDU) including an RLC header, the RLC headerincluding a segmentation information (SI) field indicating whether theRLC PDU includes a complete RLC data unit which is the RLC data unit, afirst segment of the RLC data unit, a middle segment of the RLC dataunit or a last segment of the RLC data unit, and transmit the RLC PDU toa receiving device via the transceiver, wherein the RLC header furtherincludes a segment offset (SO) field, in case that the SI fieldindicates that the RLC PDU includes the middle segment of the RLC dataunit or the last segment of the RLC data unit, wherein the RLC headerdoes not include the SO field, in case that the SI field indicates thatthe RLC PDU includes the first segment of the RLC data unit or thecomplete RLC data unit, and wherein the SO field indicates a position ofa segment of the RLC data unit within the RLC data unit.
 7. Thetransmitting device of claim 6, wherein the SI field indicates whetherthe SO field is included in the RLC header.
 8. The transmitting deviceof claim 6, wherein the SO field indicates the position within the RLCdata unit to which a first byte of the segment of the RLC data unitcorresponds.
 9. The transmitting device of claim 6, wherein the at leastone processor is further configured to: generate another RLC PDU for aretransmission of the RLC data unit, and transmit the another RLC PDU tothe receiving device via the transceiver, and wherein an RLC header forthe another RLC PDU includes the SI field without the SO field, in casethat the SI field indicates that the RLC PDU includes the first segmentof the RLC data unit or the complete RLC data unit.
 10. The transmittingdevice of claim 6, wherein the RLC header further includes a sequencenumber (SN) field, a data/control (D/C) field, and a polling bit (P)field, and wherein the RLC header does not include a re-segmentationflag (RF) field, a framing information (FI) field, a last segment flag(LSF) field and an extension bit (E) field.
 11. A method for receivingdata by a receiving device in a wireless communication system, themethod comprising: receiving a radio link control (RLC) protocol dataunit (PDU) from a transmitting device; and identifying an RLC header andan RLC data unit from the RLC PDU, the RLC header including asegmentation information (SI) field indicating whether the RLC PDUincludes a complete RLC data unit which is the RLC data unit, a firstsegment of the RLC data unit, a middle segment of the RLC data unit or alast segment of the RLC data unit, wherein the RLC header furtherincludes a segment offset (SO) field, in case that the SI fieldindicates that the RLC PDU includes the middle segment of the RLC dataunit or the last segment of the RLC data unit, wherein the RLC headerdoes not include the SO field, in case that the SI field indicates thatthe RLC PDU includes the first segment of the RLC data unit or thecomplete RLC data unit, and wherein the SO field indicates a position ofa segment of the RLC data unit within the RLC data unit.
 12. The methodof claim 11, wherein the SI field indicates whether the SO field isincluded in the RLC header.
 13. The method of claim 11, wherein the SOfield indicates the position within the RLC data unit to which a firstbyte of the segment of the RLC data unit corresponds.
 14. The method ofclaim 11, wherein the method further comprises receiving another RLC PDUfor a retransmission of the RLC data unit from the transmitting device,and wherein an RLC header for the another RLC PDU includes the SI fieldwithout the SO field, in case that the SI field indicates that the RLCPDU includes the first segment of the RLC data unit or the complete RLCdata unit.
 15. The method of claim 11, wherein the RLC header furtherincludes a sequence number (SN) field, a data/control (D/C) field, and apolling bit (P) field, and wherein the RLC header does not include are-segmentation flag (RF) field, a framing information (FI) field, alast segment flag (LSF) field and an extension bit (E) field.
 16. Areceiving device for receiving data in a wireless communication system,the receiving device comprising: a transceiver; and at least oneprocessor configured to: receive a radio link control (RLC) protocoldata unit (PDU) from a transmitting device via the transceiver, andidentify an RLC header and an RLC data unit from the RLC PDU the RLCheader including a segmentation information (SI) field indicatingwhether the RLC PDU includes a complete RLC data unit which is the RLCdata unit, a first segment of the RLC data unit, a middle segment of theRLC data unit or a last segment of the RLC data unit, wherein the RLCheader further includes a SO field, in case that the SI field indicatesthat the RLC PDU includes the middle segment of the RLC data unit or thelast segment of the RLC data unit, wherein the RLC header does notinclude the SO field, in case that the SI field indicates that the RLCPDU includes the first segment of the RLC data unit or the complete RLCdata unit, and wherein the SO field indicates a position of a segment ofthe RLC data unit within the RLC data unit.
 17. The receiving device ofclaim 16, wherein the SI field indicates whether the SO field isincluded in the RLC header.
 18. The receiving device of claim 16,wherein the SO field indicates the position within the RLC data unit towhich a first byte of the segment of the RLC data unit corresponds. 19.The receiving device of claim 16, wherein the at least one processor isfurther configured to receive another RLC PDU for a retransmission ofthe RLC data unit from the transmitting device via the transceiver, andwherein an RLC header for the another RLC PDU includes the SI fieldwithout the SO field, in case that the SI field indicates that the RLCPDU includes the first segment of the RLC data unit or the complete RLCdata unit.
 20. The receiving device of claim 16, wherein the RLC headerfurther includes a sequence number (SN) field, a data/control (D/C)field, and a polling bit (P) field, and wherein the RLC header does notinclude a re-segmentation flag (RF) field, a framing information (FI)field, a last segment flag (LSF) field and an extension bit (E) field.